| 2.1 |
Approval of the agenda |
|
| R2-2407901 |
Agenda for RAN2#127bis |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2407902 |
RAN2#127 Meeting Report |
MCC |
| R2-2409202 |
RAN2#127 Meeting Report |
MCC |
| R2-2409210 |
RAN2#127 Meeting Report |
MCC |
| 2.5 |
Others |
|
| R2-2407903 |
RAN2 Handbook |
MCC |
| R2-2409400 |
IRIS² - The New EU Programme Providing Secure Communications Via Satellites |
ESA |
| R2-2409411 |
LS on Invitation to Join a Basketball Game (R3-245824; contact: ZTE) |
RAN3 |
| 4.1 |
EUTRA corrections Rel-17 and earlier |
|
| R2-2408568 |
Correction to NR Beam Reporting in LTE RRC |
Apple, |
| R2-2408569 |
Correction to NR Beam Reporting in LTE RRC |
Apple, |
| R2-2408570 |
Correction to NR Beam Reporting in LTE RRC |
Apple, |
| R2-2408571 |
Correction to NR Beam Reporting in LTE RRC |
Apple, ZTE Corporation |
| R2-2408669 |
UE capability constraints for Qoffsettemp |
Nokia Poland |
| R2-2409129 |
Correction on eutra-CGI-Reporting-ENDC and utra-GERAN-CGI-Reporting-ENDC |
Huawei, HiSilicon |
| R2-2409130 |
Correction on eutra-CGI-Reporting-ENDC and utra-GERAN-CGI-Reporting-ENDC |
Huawei, HiSilicon |
| R2-2409131 |
Correction on eutra-CGI-Reporting-ENDC and utra-GERAN-CGI-Reporting-ENDC |
Huawei, HiSilicon |
| R2-2409132 |
Correction on eutra-CGI-Reporting-ENDC and utra-GERAN-CGI-Reporting-ENDC |
Huawei, HiSilicon |
| R2-2409133 |
Correction on eutra-CGI-Reporting-NRDC and NR-CGI-Reporting-NRDC |
Huawei, HiSilicon |
| R2-2409134 |
Correction on eutra-CGI-Reporting-NRDC and NR-CGI-Reporting-NRDC |
Huawei, HiSilicon |
| R2-2409135 |
Correction on eutra-CGI-Reporting-NRDC and NR-CGI-Reporting-NRDC |
Huawei, HiSilicon |
| R2-2409136 |
Correction on eutra-CGI-Reporting-NRDC and NR-CGI-Reporting-NRDC |
Huawei, HiSilicon |
| R2-2409195 |
Correction to NR Beam Reporting in LTE RRC |
Apple, ZTE Corporation |
| R2-2409196 |
Correction to NR Beam Reporting in LTE RRC |
Apple, ZTE Corporation |
| R2-2409197 |
Correction to NR Beam Reporting in LTE RRC |
Apple, ZTE Corporation |
| R2-2409198 |
Correction to NR Beam Reporting in LTE RRC |
Apple, ZTE Corporation |
| 4.3 |
Positioning corrections Rel-16 and earlier |
|
| R2-2408774 |
Correction to the need code of AssistanceDataSIBelement |
Huawei, HiSilicon |
| R2-2408775 |
Correction to the need code of AssistanceDataSIBelement |
Huawei, HiSilicon |
| R2-2408776 |
Correction to the need code of AssistanceDataSIBelement |
Huawei, HiSilicon |
| R2-2408777 |
Correction to the need code in AssistanceDataSIBelement-r18 |
Huawei, HiSilicon |
| 5.1.1 |
Stage 2 and Organisational |
|
| R2-2408234 |
Gap requirement for CSI-RS based measurements and inter-RAT measurements |
Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
| R2-2408235 |
Gap requirement for CSI-RS based measurements and inter-RAT measurements |
Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
| R2-2408236 |
Gap requirement for CSI-RS based measurements and inter-RAT measurements |
Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
| R2-2408644 |
Maximum number of configured CCs |
Nokia, Nokia Shanghai Bell |
| 5.1.2.1 |
MAC |
|
| R2-2408348 |
Correction on Random Access Preamble group B for 2-step RA and 4-step RA |
ASUSTeK |
| R2-2408349 |
Correction on Random Access Preamble group B for 2-step RA and 4-step RA |
ASUSTeK |
| R2-2408350 |
Correction on Random Access Preamble group B for 2-step RA and 4-step RA |
ASUSTeK |
| R2-2409079 |
Correction to available UL-SCH resources in SR triggering |
Samsung (Rapporteur), Ericsson, Spreadtrum |
| R2-2409080 |
Correction to available UL-SCH resources in SR triggering |
Samsung (Rapporteur), Ericsson, Spreadtrum |
| R2-2409081 |
Correction to available UL-SCH resources in SR triggering |
Samsung (Rapporteur), Ericsson, Spreadtrum |
| 5.1.2.2 |
RLC PDCP SDAP BAP |
|
| R2-2408266 |
Correction on BH RLC channel and RLC channel |
Xiaomi, Apple |
| R2-2408267 |
Correction on BH RLC channel and RLC channel |
Xiaomi, Apple |
| R2-2408268 |
Correction on BH RLC channel and RLC channel |
Xiaomi, Apple |
| R2-2408989 |
Miscellaneous corrections on BAP for IAB |
Huawei, HiSilicon (Rapporteur) |
| R2-2408990 |
Miscellaneous corrections on BAP for IAB |
Huawei, HiSilicon (Rapporteur) |
| R2-2408991 |
Miscellaneous corrections on BAP for IAB |
Huawei, HiSilicon (Rapporteur) |
| 5.1.3.1 |
NR RRC |
|
| R2-2407918 |
LS on higher layer parameters for DCI format 2_3 (R1-2407534; contact: CATT) |
RAN1 |
| R2-2408200 |
Correction on IE SRS-CarrierSwitching |
CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation, CMCC |
| R2-2408201 |
Correction on IE SRS-CarrierSwitching |
CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation |
| R2-2408202 |
Correction on IE SRS-CarrierSwitching |
CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation |
| R2-2408203 |
Correction on IE SRS-CarrierSwitching |
CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation |
| R2-2408204 |
DRAFT Reply LS on higher layer parameters for DCI format 2_3 |
CATT |
| R2-2408245 |
Minor Corrections on TS38.331 |
vivo |
| R2-2408246 |
Minor Corrections on TS38.331 |
vivo |
| R2-2408247 |
Minor Corrections on TS38.331 |
vivo |
| R2-2408248 |
Minor Corrections on TS38.331 |
vivo |
| R2-2408809 |
Correction to Ocn description in measurement event |
Ericsson |
| R2-2408810 |
Correction to Ocn description in measurement event |
Ericsson |
| R2-2408811 |
Correction to Ocn description in measurement event |
Ericsson |
| R2-2408812 |
Correction to Ocn description in measurement event |
Ericsson |
| R2-2408844 |
Correction on IE perRAInfoList for CEF report |
Huawei, HiSilicon |
| R2-2408845 |
Correction on IE perRAInfoList for CEF report and SCGFailureInformation |
Huawei, HiSilicon |
| R2-2408846 |
Correction on IE perRAInfoList for CEF report and SCGFailureInformation |
Huawei, HiSilicon |
| R2-2408888 |
RRC correction on field descriptions of PUSCH-ServingCellConfig |
Philips International B.V. |
| R2-2408889 |
RRC correction on field descriptions of PUSCH-ServingCellConfig |
Philips International B.V. |
| R2-2408890 |
RRC correction on field descriptions of PUSCH-ServingCellConfig |
Philips International B.V. |
| R2-2408891 |
RRC correction on field descriptions of PUSCH-ServingCellConfig |
Philips International B.V. |
| R2-2409285 |
Correction on IE SRS-CarrierSwitching |
CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation, CMCC |
| R2-2409286 |
Correction on IE SRS-CarrierSwitching |
CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation |
| R2-2409287 |
Correction on IE SRS-CarrierSwitching |
CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation |
| R2-2409288 |
Correction on IE SRS-CarrierSwitching |
CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation |
| R2-2409298 |
Correction on IE perRAInfoList for SCGFailureInformation |
Huawei, HiSilicon |
| R2-2409299 |
Correction on IE perRAInfoList for SCGFailureInformation |
Huawei, HiSilicon |
| 5.1.3.2 |
UE capabilities |
|
| R2-2408469 |
Corrections on parallelTx capabilities for inter-band and intra-band |
Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2408470 |
Corrections on parallelTx capabilities for inter-band and intra-band |
Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2408471 |
Corrections on parallelTx capabilities for inter-band and intra-band |
Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2408472 |
Corrections on parallelTx capabilities for inter-band and intra-band |
Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2408514 |
Clarification on NR PDCP capability |
ZTE Corporation |
| R2-2408515 |
Correction on NR PDCP capability |
ZTE Corporation |
| R2-2408516 |
Correction on NR PDCP capability |
ZTE Corporation |
| R2-2408517 |
Correction on NR PDCP capability |
ZTE Corporation |
| R2-2408518 |
Correction on NR PDCP capability |
ZTE Corporation |
| R2-2408898 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2408899 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2408900 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2408911 |
Missing NR-DC parameters branches and DCI format 2_3 |
Ericsson |
| R2-2409289 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2409290 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2409291 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2409292 |
Correction to missing NR-DC parameters branches |
Ericsson |
| R2-2409293 |
Correction to missing NR-DC parameters branches |
Ericsson |
| R2-2409294 |
Correction to missing NR-DC parameters branches |
Ericsson |
| R2-2409305 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2409306 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2409307 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2409383 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2409384 |
Clarification on inter-band handover enhancements capabilities |
Qualcomm Inc. |
| R2-2409401 |
Correction to missing NR-DC parameters branches |
Ericsson |
| 5.1.3.3 |
Other |
|
| R2-2409034 |
Correction to Relaxed measurement |
LG Electronics, Nokia, Samsung, Ericsson |
| R2-2409036 |
Correction to Relaxed measurement |
LG Electronics, Nokia, Samsung, Ericsson |
| R2-2409037 |
Correction to Relaxed measurement |
LG Electronics, Nokia, Samsung, Ericsson |
| R2-2409282 |
Correction to Relaxed measurement |
LG Electronics, Nokia, Samsung, Ericsson |
| R2-2409283 |
Correction to Relaxed measurement |
LG Electronics, Nokia, Samsung, Ericsson |
| R2-2409284 |
Correction to Relaxed measurement |
LG Electronics, Nokia, Samsung, Ericsson |
| R2-2409308 |
LS on Relaxed measurement |
RAN2 |
| 5.2 |
NR V2X |
|
| R2-2408541 |
Discussion on intra-UE prioritization |
ZTE Corporation, Nokia |
| R2-2408585 |
Corrections on UE behaviour upon reception of RRCReconfigCompleteSL |
Apple |
| R2-2408586 |
Corrections on UE behaviour upon reception of RRCReconfigCompleteSL |
Apple |
| R2-2408587 |
Corrections on UE behaviour upon reception of RRCReconfigCompleteSL |
Apple |
| R2-2408913 |
RRC correction on sl-X-Overhead field description of SL-ResourcePool |
Philips International B.V. |
| R2-2408914 |
RRC correction on sl-X-Overhead field description of SL-ResourcePool |
Philips International B.V. |
| R2-2408915 |
RRC correction on sl-X-Overhead field description of SL-ResourcePool |
Philips International B.V. |
| R2-2409363 |
Correction on intra-UE prioritization |
ZTE Corporation |
| R2-2409364 |
Correction on intra-UE prioritization |
ZTE Corporation |
| R2-2409365 |
Correction on intra-UE prioritization |
ZTE Corporation |
| R2-2409366 |
RRC correction on sl-X-Overhead field description of SL-ResourcePool |
Philips International B.V. |
| R2-2409367 |
RRC correction on sl-X-Overhead field description of SL-ResourcePool |
Philips International B.V. |
| R2-2409368 |
RRC correction on sl-X-Overhead field description of SL-ResourcePool |
Philips International B.V. |
| 5.3 |
NR Positioning Support |
|
| R2-2408213 |
Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning |
ZTE Corporation |
| R2-2408214 |
Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning |
ZTE Corporation |
| R2-2408215 |
Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning |
ZTE Corporation |
| 6.1.1 |
Stage 2 and Organisational |
|
| R2-2407913 |
LS response on power control parameters for unified TCI state framework (R1-2407424; contact: Ericsson) |
RAN1 |
| R2-2407929 |
Reply to LS on IE supportedBandwidthCombinationSetIntraENDC and IE intraBandENDC-Support (R4-2412923; contact: Google) |
RAN4 |
| R2-2408366 |
Correction on location based measurements in NR NTN |
CATT, Nokia, Nokia Shanghai Bell |
| R2-2408367 |
Correction on location based measurements in NR NTN |
CATT, Nokia, Nokia Shanghai Bell |
| R2-2408853 |
Enhanced channel raster for (e)RedCap UE |
Ericsson |
| R2-2409295 |
Mandatory support of Enhanced channel raster by RedCap UE |
Ericsson |
| R2-2409296 |
Mandatory support of Enhanced channel raster by RedCap UE |
Ericsson |
| 6.1.2 |
User Plane corrections |
|
| R2-2408179 |
Discussion on Type-3 PHR for mTRP PUSCH Repetition |
CATT |
| R2-2408467 |
Correction on HARQ process |
Samsung, Ericsson, Nokia, LG Electronics Inc., Qualcomm Incorporated, Apple, ZTE, CATT |
| R2-2408468 |
Correction on HARQ process |
Samsung, Ericsson, Nokia, LG Electronics Inc., Qualcomm Incorporated, Apple, ZTE, CATT |
| R2-2408813 |
Correction on use of recommended of IAB-MT beam indication |
Ericsson, Samsung |
| R2-2408814 |
Correction on use of recommended of IAB-MT beam indication. |
Ericsson, Samsung |
| R2-2408827 |
Corrections to validity of configured uplink grant for SDT |
Samsung |
| R2-2409043 |
Correction on PHR for mTRP PUSCH repetition (R17) |
LG Electronics Inc., MediaTek Inc. |
| R2-2409044 |
Correction on PHR for mTRP PUSCH repetition (R17) |
LG Electronics Inc., MediaTek Inc. |
| R2-2409045 |
Correction on PHR for mTRP PUSCH repetition (R17) |
LG Electronics Inc., MediaTek Inc. |
| R2-2409046 |
Correction on PHR for mTRP PUSCH repetition |
LG Electronics Inc., MediaTek Inc. |
| R2-2409047 |
Correction on PHR for mTRP PUSCH repetition |
LG Electronics Inc., MediaTek Inc. |
| R2-2409048 |
Correction on PHR for mTRP PUSCH repetition |
LG Electronics Inc., MediaTek Inc. |
| R2-2409120 |
Correction on drx HARQ RTT timer in NTN |
LG Electronics Inc. |
| R2-2409121 |
Correction on drx HARQ RTT timer in NTN |
LG Electronics Inc. |
| R2-2409123 |
Correction on drx HARQ RTT timer in NTN |
LG Electronics Inc. |
| R2-2409219 |
Correction on use of recommended of IAB-MT beam indication |
Ericsson, Samsung |
| R2-2409220 |
Corrections to validity of configured uplink grant for SDT |
Samsung |
| 6.1.3 |
Control Plane corrections |
|
| R2-2408023 |
Clarification on the maximum number of SI for Msg3-based on-demand SI request |
Xiaomi |
| R2-2408024 |
Option 1 for clarifying the maximum number of SI for Msg3-based on-demand SI request (Rel-17) |
Xiaomi |
| R2-2408025 |
Option 1 for clarifying the maximum number of SI for Msg3-based on-demand SI request (Rel-18) |
Xiaomi |
| R2-2408026 |
Option 2 for clarifying the maximum number of SI for Msg3-based on-demand SI request (Rel-17) |
Xiaomi |
| R2-2408027 |
Option 2 for clarifying the maximum number of SI for Msg3-based on-demand SI request (Rel-18) |
Xiaomi |
| R2-2408503 |
Clarification of MeasurementTimingConfiguration use |
Vodafone, Ericsson |
| R2-2408506 |
Clarification of MeasurementTimingConfiguration use |
Vodafone, Ericsson |
| 6.1.3.1 |
NR RRC |
|
| R2-2407970 |
Further discussion on RAN4 LS R2-2406225 for Rel-17 NR NTN |
CATT |
| R2-2408231 |
Corrections to NR NTN (R17) |
Huawei, HiSilicon |
| R2-2408232 |
Corrections to NR NTN (R18) |
Huawei, HiSilicon |
| R2-2408323 |
Correction to unified TCI signalling |
MediaTek Inc. |
| R2-2408324 |
Correction to unified TCI signalling |
MediaTek Inc. |
| R2-2408651 |
Corrections on measurement gap configruation |
ZTE Corporation, Sanechips |
| R2-2408652 |
Corrections on measurement gap configruation |
ZTE Corporation, Sanechips |
| R2-2408653 |
Corrections to mobility history information |
ZTE Corporation, Sanechips |
| R2-2408704 |
Correction on deprioritisationTimer field description |
Nokia |
| R2-2408726 |
Correction on deprioritisationTimer field description |
Nokia |
| R2-2408730 |
Correction for CFRA configuration due to PRACH partitioning |
Huawei, HiSilicon, ZTE Corporation, Ericsson, Mediatek |
| R2-2408731 |
Correction for CFRA configuration due to PRACH partitioning |
Huawei, HiSilicon, ZTE Corporation, Ericsson, Mediatek |
| R2-2408821 |
Correction and clarifications on MHI in DC |
Ericsson |
| R2-2408822 |
Correction and clarifications on MHI in DC |
Ericsson |
| R2-2408851 |
Definition of IE AdditionalPCIIndex |
Ericsson |
| R2-2408852 |
Definition of IE AdditionalPCIIndex |
Ericsson |
| R2-2409010 |
Correction on storing time spent with no PSCell when entering any cell selection state |
Samsung |
| R2-2409012 |
Correction on storing time spent with no PSCell when entering any cell selection state |
Samsung |
| R2-2409090 |
Corrections to NR NTN (R17) |
Huawei, HiSilicon, CMCC |
| R2-2409091 |
Corrections to NR NTN (R18) |
Huawei, HiSilicon, CMCC |
| R2-2409102 |
Correction on the RLM and BFD relaxation |
Google |
| R2-2409104 |
Correction on the RLM and BFD relaxation |
Google |
| R2-2409124 |
Miscellaneous non-controversial corrections Set XXIII |
Ericsson |
| R2-2409125 |
Miscellaneous non-controversial corrections Set XXIII |
Ericsson |
| R2-2409238 |
Corrections to NR NTN (R17) |
Huawei, HiSilicon, CMCC |
| R2-2409240 |
Corrections to NR NTN (R18) |
Huawei, HiSilicon, CMCC |
| 6.1.3.2 |
UE capabilities |
|
| R2-2408371 |
Network signalling of maximum number of UL segments |
Qualcomm Incorporated, AT&T |
| R2-2408372 |
Introduction of network signalling of maximum number of UL segments |
Qualcomm Incorporated |
| R2-2408373 |
Introduction of network signalling of maximum number of UL segments |
Qualcomm Incorporated |
| R2-2408476 |
Correction on UE capabilities for TCI state indication |
Huawei, HiSilicon |
| R2-2408477 |
Correction on UE capabilities for TCI state indication |
Huawei, HiSilicon |
| R2-2408478 |
Correction on UE capabilities for TCI state indication |
Huawei, HiSilicon |
| R2-2408479 |
Correction on UE capabilities for TCI state indication |
Huawei, HiSilicon |
| R2-2409300 |
Introduction of network signalling of maximum number of UL segments |
Qualcomm Incorporated |
| R2-2409301 |
Introduction of network signalling of maximum number of UL segments |
Qualcomm Incorporated |
| R2-2409302 |
Introduction of network signalling of maximum number of UL segments |
Qualcomm Incorporated |
| R2-2409303 |
Introduction of network signalling of maximum number of UL segments |
Qualcomm Incorporated |
| R2-2409304 |
LS on UL RRC message segmentation for UECapabilityInformation |
Qualcomm Incorporated |
| R2-2409309 |
Correction on UE capabilities for TCI state indication |
Huawei, HiSilicon |
| R2-2409310 |
Correction on UE capabilities for TCI state indication |
Huawei, HiSilicon |
| R2-2409311 |
Correction on UE capabilities for TCI state indication |
Huawei, HiSilicon |
| R2-2409312 |
Correction on UE capabilities for TCI state indication |
Huawei, HiSilicon |
| R2-2409313 |
LS on UL RRC message segmentation for UECapabilityInformation |
RAN2 |
| 6.1.3.3 |
Other |
|
| R2-2408743 |
Correction on emergency call back when eDRX is configured in RRC_INACTIVE |
Nokia |
| R2-2408744 |
Correction on emergency call back when eDRX is configured in RRC_INACTIVE |
Nokia |
| 6.2 |
NR Sidelink relay |
|
| R2-2407996 |
Clarification on the L2 U2N Remote UE Measurement |
CATT |
| R2-2407997 |
Clarification on the L2 U2N Remote UE Measurement |
CATT |
| R2-2408269 |
Correction on PC5/Uu RLC channel and RLC channel |
Xiaomi, Apple, Nokia, OPPO |
| R2-2408270 |
Correction on PC5/Uu RLC channel and RLC channel |
Xiaomi, Apple, Nokia, OPPO |
| R2-2408663 |
Clarification on definition of PC5 and Uu Relay RLC channel |
Huawei, HiSilicon |
| R2-2408664 |
Clarification on definition of PC5 and Uu Relay RLC channel |
Huawei, HiSilicon |
| R2-2408877 |
Correction on the SL Relay Measurement |
Ericsson |
| R2-2408878 |
Correction on the SL Relay Measurement |
Ericsson |
| R2-2408886 |
RRC correction on NR sidelink discovery |
Philips International B.V. |
| R2-2408887 |
RRC correction on NR sidelink discovery |
Philips International B.V. |
| R2-2409054 |
Correction on field description of reportOnLeave for U2N Relay |
OPPO |
| R2-2409117 |
Correction on field description of reportOnLeave for U2N Relay |
OPPO |
| R2-2409260 |
Miscellaneous CR for Rel-17 SL relay |
Huawei, HiSilicon, Philips International B.V., OPPO |
| R2-2409261 |
Miscellaneous CR for Rel-17 SL relay |
Huawei, HiSilicon, Philips International B.V., OPPO |
| 6.4 |
NR positioning enhancements |
|
| R2-2408778 |
Correction to MAC for R17 POS |
Huawei, HiSilicon |
| R2-2408779 |
Correction to MAC for R17 POS |
Huawei, HiSilicon |
| R2-2409078 |
Corrections related to posSIB segmentation |
Ericsson |
| R2-2409083 |
Corrections related to posSIB segmentation |
Ericsson |
| R2-2409175 |
Corrections related to posSIB segmentation |
Ericsson |
| R2-2409177 |
Corrections related to posSIB segmentation |
Ericsson |
| 6.6 |
NR Sidelink enhancements |
|
| R2-2408361 |
Misc RRC corrections for SL enhancements |
Huawei, HiSilicon |
| R2-2408362 |
Misc RRC corrections for SL enhancements |
Huawei, HiSilicon |
| R2-2408539 |
Correction on unit of SL DRX timer |
ZTE Corporation |
| R2-2408540 |
Correction on unit of SL DRX timer |
ZTE Corporation |
| R2-2408639 |
Discussion on MAC correction for IUC's resource selection |
LG, OPPO, Ericsson |
| R2-2408642 |
Discussion on MAC correction for IUC's resource selection |
LG, OPPO, Ericsson |
| R2-2408680 |
Correction to MAC on random resource selection for sidelink |
Ericsson |
| R2-2408681 |
Correction to MAC on random resource selection for sidelink |
Ericsson |
| R2-2409369 |
Correction to MAC on random resource selection for sidelink |
Ericsson |
| R2-2409370 |
Correction to MAC on random resource selection for sidelink |
Ericsson |
| 7.0.1 |
UE Capabilities |
|
| R2-2407909 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#118 (R1-2407387; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2407932 |
LS on RAN4 UE feature list for Rel-18 (version 6) (R4-2414459; contact: CMCC) |
RAN4 |
| R2-2408738 |
Guideline on implementing xDD/FRx-differentation in per UE capability |
Huawei, HiSilicon |
| R2-2408761 |
Regarding missing capability for DPC |
Ericsson |
| R2-2409386 |
Guidelines on implementing FRx/xDD differentiation in per UE capability |
Huawei, HiSilicon |
| R2-2409387 |
Guidelines on implementing FRx/xDD differentiation in per UE capability |
Huawei, HiSilicon |
| 7.0.2.1 |
RACH-less HO |
|
| R2-2408233 |
Correction to RACH-less HO [RACH-lessHO] |
Huawei, HiSilicon, CATT, Apple, CMCC, Nokia, Nokia Shanghai Bell |
| R2-2408796 |
Rapporteur CR for RACH-less LTM and RACH-less HO [RACH-lessHO] |
Huawei, HiSilicon |
| R2-2409159 |
Correction on RACH-less handover fallback [RACH-lessHO] |
Huawei, HiSilicon, Samsung |
| R2-2409406 |
Correction on RACH-less handover fallback [RACH-lessHO] |
Huawei, HiSilicon, Samsung, Qualcomm, CATT |
| 7.0.2.3 |
NR support for UAV |
|
| R2-2408404 |
Correction on handling for simulMultiTriggerSingleMeasReport |
ZTE |
| 7.0.2.4 |
Mobile Terminated Small Data Transmission |
|
| R2-2408020 |
Correction on SDT Capability for NR-NTN Case |
vivo, ZTE Corporation |
| R2-2408230 |
Impacts on RAN2 for supporting of partial context transfer for co-existence of SDT and Multicast in RRC_INACTIVE |
SHARP Corporation |
| R2-2408797 |
Rapporteur CR for MT-SDT and CG-SDT enhancements [CG-SDTenh] |
Huawei, HiSilicon |
| R2-2409032 |
Rapporteur CR for MT-SDT and CG-SDT enhancement [CG-SDTenh] |
Huawei, HiSilicon |
| 7.0.2.5 |
IDC enhancements for NR and MR-DC |
|
| R2-2408937 |
Correction on the idc-TDM-AssistanceConfig |
Huawei, HiSilicon, Xiaomi, Nokia, Intel Corporation, Ericsson, Apple, Samsung |
| 7.0.2.7 |
Timing Resiliency and URLLC Enh |
|
| R2-2408271 |
Addition of URLLC related UE capability for the clock information mechanism |
Huawei, Hisilicon |
| 7.0.2.8 |
Enhanced support of reduced capability NR devices |
|
| R2-2408028 |
Corrections on capabilities for eRedCap |
Huawei, HiSilicon, LG Electronics Inc., Intel Corporation |
| R2-2408127 |
Correction on eRedCap UE fallback to use RedCap resource |
vivo, Guangdong Genius |
| R2-2408969 |
Clarification on the definition of eRedCap UEs |
Ericsson, Sequans Communications |
| R2-2409205 |
Clarification on the definition of eRedCap UEs |
Ericsson, Sequans Communications |
| R2-2409395 |
Corrections on capabilities for eRedCap |
Huawei, HiSilicon, LG Electronics Inc., Intel Corporation |
| 7.0.2.9 |
Further NR coverage enhancements |
|
| R2-2408272 |
Correction on CE-only BWP(R17) |
Huawei, Hisilicon |
| R2-2408273 |
Correction on CE-only BWP(R18) |
Huawei, Hisilicon |
| R2-2408509 |
Clarification on CFRA with MSG1 repetition for (e)RedCap in RRC |
Huawei, HiSilicon (CE RRC Rapporteur) |
| R2-2408972 |
Clarifications on DPC field in PHR MAC CE |
Samsung |
| 7.0.2.10 |
Network energy savings for NR |
|
| R2-2408340 |
Discussion on servingCellMO |
Huawei, HiSilicon, Apple |
| R2-2408387 |
Correction on CSI-ReportSubConfig field descriptions for NES |
Ericsson |
| R2-2408443 |
Network energy savings for NR rapporteur RRC CR |
Huawei, HiSilicon |
| R2-2408910 |
Conditions for L1 configuration for cell DTXDRX |
Ericsson |
| R2-2409392 |
Report of [AT127bis][008][NES] SSB-less Scell (Huawei) |
Huawei, HiSilicon |
| 7.0.2.11 |
Others |
|
| R2-2408157 |
Discussion on HARQ feedback for MBS in NTN |
OPPO |
| R2-2408158 |
Draft LS on HARQ feedback for MBS in NTN |
OPPO |
| R2-2408519 |
Clarification on band selection procedure |
ZTE Corporation |
| R2-2408636 |
Correction on band selection procedure |
ZTE Corporation |
| R2-2408815 |
Coexistence of LTM with (e)RedCap |
Ericsson |
| R2-2408816 |
Coexistence of NCR, LTM and CPAC with (e)RedCap |
Ericsson |
| 7.2.1 |
Organizational |
|
| R2-2407904 |
Reply on LS on the maximum number of devices supported in SLPP (C1-245040; contact: vivo) |
CT1 |
| R2-2407908 |
LS on a RRC parameter needed for the sequence generation of PSCCH DMRS for a dedicated SL PRS resource pool (R1-2407377; contact: Qualcomm) |
RAN1 |
| R2-2407911 |
Reply LS on synchronization source change at the transmitting anchor UE in SL positioning (R1-2407401; contact: Ericsson) |
RAN1 |
| R2-2407928 |
LS on synchronization source change at the transmitting anchor UE in SL positioning (R4-2410352; contact: Ericsson) |
RAN4 |
| R2-2407935 |
Reply on Clarifications of Relative Velocity (S2-2409386; contact: Nokia) |
SA2 |
| R2-2407981 |
Discussion on reply LS on the maximum number of devices supported in SLPP |
vivo |
| R2-2408939 |
draft LS reply on synchronization source change at the transmitting anchor UE in SL positioning |
Ericsson |
| R2-2409251 |
Clarification on the maximum number of other UEs in sidelink positioning |
vivo |
| R2-2409252 |
Reply LS on the maximum number of devices supported in SLPP |
RAN2 |
| R2-2409253 |
draft LS reply on synchronization source change at the transmitting anchor UE in SL positioning |
Ericsson |
| R2-2409267 |
Reply LS on synchronization source change at the transmitting anchor UE in SL positioning |
RAN2 |
| 7.2.2 |
Stage 2 |
|
| R2-2408216 |
Correction on assistance data transfer in SL positioning for stage-2 |
ZTE Corporation |
| R2-2408721 |
DRX and PRS alignment for positioning |
Sony, Ericsson, Intel Corporation |
| R2-2409161 |
Correction of Pre-configuration SRS activation |
Ericsson |
| R2-2409259 |
Correction on assistance data transfer in SL positioning for stage-2 |
ZTE Corporation |
| 7.2.3 |
SLPP corrections |
|
| R2-2407944 |
Corrections of location time stamp, RSTD and RTOA report |
CATT |
| R2-2408513 |
Missing additional measurements for SL-TDOA and SL-TOA |
Qualcomm Incorporated |
| R2-2408790 |
Correction on SLPP |
Huawei, HiSilicon |
| R2-2408973 |
Miscellaneous corrections to SLPP specification |
Intel Corporation |
| R2-2409254 |
Miscellaneous corrections to SLPP specification |
Intel Corporation |
| R2-2409255 |
Corrections of location time stamp, RSTD and RTOA report |
CATT |
| R2-2409256 |
LS on Additional Measurements for SL-TDOA and SL-TOA |
RAN2 |
| R2-2409257 |
Correction on SLPP |
Huawei, HiSilicon |
| R2-2409268 |
Corrections of location time stamp, RSTD and RTOA report |
CATT |
| 7.2.4 |
LPP corrections |
|
| R2-2408217 |
Correction on remaining issues in LPP |
ZTE Corporation |
| 7.2.5 |
RRC corrections |
|
| R2-2407945 |
Correction of SL CBR Range and level parameters and activation of srs-PosRRC-InactiveValidityAreaNonPreConfig |
CATT |
| R2-2408250 |
Discussion on RRC miscellaneous issues for sidelink positioning |
vivo |
| R2-2408789 |
Correction for positioning SRS CA in RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2408864 |
RRC correction on NR sidelink positioning |
Philips International B.V. |
| R2-2408935 |
Miscellaneous RRC Positioning Correction |
Ericsson |
| R2-2408940 |
Sidelink Positioning Postponed issues for RRC |
Ericsson |
| R2-2409258 |
LS to RAN1 on CBR range |
RAN2 |
| 7.2.6 |
MAC corrections |
|
| R2-2408351 |
Correction on prioritization between SR and SL-PRS transmission |
ASUSTeK |
| R2-2408787 |
Rapporteur CR to MAC spec for R18 Positioning |
Huawei, HiSilicon |
| R2-2409158 |
Correction of misplaced else condition of SL Positioning clause |
Ericsson |
| 7.2.7 |
Corrections to other specifications |
|
| R2-2408788 |
Rapporteur CR to IDLE mode procedure for R18 Positioning |
Huawei, HiSilicon |
| R2-2408885 |
Correction on NR sidelink operation for positioning/ranging |
Philips International B.V. |
| 7.4.1 |
Organizational |
|
| R2-2407915 |
LS on missing RRC parameters for early UL sync PRACH transmission for LTM (R1-2407447; contact: Fujitsu) |
RAN1 |
| R2-2407924 |
LS on Early TA acquisition for the inter-DU scenario (R3-244793; contact: Google) |
RAN3 |
| R2-2408432 |
Discussion for Replying LS on inter-DU Early TA acquisition and Preamble Resources for PDCCH order in LTM |
Google |
| R2-2409373 |
L3 measurement based LTM support over F1 |
RAN2 |
| R2-2409382 |
Reply LS on L3 measurement based LTM support over F1 (R3-245710; contact: Vodafone) |
RAN3 |
| 7.4.2 |
Control plane corrections |
|
| R2-2407993 |
Issue on the power control parameters after LTM cell switch |
CATT |
| R2-2407994 |
Miscellaneous corrections for SCPAC |
CATT |
| R2-2408126 |
Correction on s-Measure for L1 measurement |
vivo |
| R2-2408258 |
Discussion and corrections on RRC and UE capability for LTM |
MediaTek Inc. |
| R2-2408325 |
Correction to LTM fast RRC processing |
MediaTek Inc. |
| R2-2408433 |
[Draft] Reply LS on Early TA acquisition for the inter-DU scenario |
Google |
| R2-2408436 |
Remaining issues for Rel18 Mobility Enhancements |
Samsung |
| R2-2408452 |
Misc state 2 corrections for LTM mobility |
Vodafone, Ericsson |
| R2-2408522 |
Corrections for mobility enhancements in stage-2 |
ZTE Corporation, Ericsson |
| R2-2408523 |
Further discussion on RAN3 LS on intra-SN SCPAC in MN format |
ZTE Corporation, CATT, Ericsson |
| R2-2408632 |
TP for Stage 2 coexistence case |
Lenovo |
| R2-2408678 |
Clarification on conditional, DAPS and LTM candidate configurations in LTM configuration |
Google |
| R2-2408751 |
SCPAC Corrections |
Nokia |
| R2-2408756 |
Clarification on LTM capabilities |
Google |
| R2-2408818 |
Misc RRC corrections for feMob |
Ericsson (Rapporteur) |
| R2-2408819 |
RRC corrections for feMob |
Ericsson |
| R2-2408820 |
Summary of RRC proposals for feMob |
Ericsson (Rapporteur) |
| R2-2408945 |
Miscellaneous Rel-18 LTM Aspects and Corrections |
Nokia |
| R2-2409137 |
LTM UE capabilities for inter-frequency L1 measurements |
Huawei, HiSilicon |
| R2-2409352 |
Reply LS on Early TA acquisition for the inter-DU scenario |
Google |
| R2-2409353 |
Misc RRC corrections for feMob |
Ericsson (Rapporteur) |
| R2-2409354 |
Summary of [AT127bis][103][MOB] |
Ericsson |
| R2-2409355 |
Misc state 2 corrections for LTM mobility |
Vodafone, Ericsson, Nokia, ZTE |
| R2-2409356 |
Report from [AT127b][104][MOB] (Nokia) |
Nokia |
| R2-2409357 |
Corrections for mobility enhancements in stage-2 |
ZTE Corporation, Ericsson |
| R2-2409358 |
Report of [AT127b][105][MOB] (ZTE) |
ZTE Corporation |
| R2-2409359 |
Reply LS on intra-SN SCPAC in MN format |
RAN2 |
| R2-2409360 |
LS on UE capabilities for inter-frequency L1 measurements for LTM |
RAN2 |
| R2-2409376 |
Reply LS on Early TA acquisition for the inter-DU scenario |
RAN2 |
| R2-2409377 |
LS on the fast RRC processing for LTM |
RAN2 |
| 7.4.3 |
User plane corrections |
|
| R2-2408262 |
Correction on BWP switching during PRACH triggered for LTM candidate cells |
MediaTek Inc. |
| R2-2408297 |
MAC corrections for LTM |
Samsung Electronics Co., Ltd |
| R2-2408755 |
Clarification to 38.321 on LTM Cell Switch UP Aspect |
ZTE Corporation |
| R2-2408784 |
Clarification on random access procedure initialization for early UL synchronization |
Google |
| R2-2408817 |
MAC corrections for feMob |
Ericsson |
| R2-2408875 |
Coexistence of UE C-DRX and RACH-less LTM |
Rakuten Mobile, Inc |
| R2-2409138 |
Miscellaneous corrections for LTM |
Huawei, HiSilicon |
| R2-2409139 |
Correction to LTM MAC CE based CFRA with MSG1 repetition |
Huawei, HiSilicon |
| R2-2409140 |
MAC CR rapporteur summary |
Huawei, HiSilicon |
| R2-2409361 |
Miscellaneous corrections for LTM |
Huawei, HiSilicon |
| R2-2409362 |
[AT127b][108][MOB] (Huawei) |
Huawei, HiSilicon |
| 7.5.2 |
Control plane corrections |
|
| R2-2408729 |
Clarification for UE capability on UL traffic information |
Huawei, HiSilicon |
| 7.5.3 |
User plane corrections |
|
| R2-2408003 |
Clarification on the SN Gap Report |
CATT |
| R2-2408481 |
Correction for stored SDUs handling when a t-Reordering expires |
Samsung |
| R2-2408528 |
Correction to DRX_SFN_COUNTER for handover case |
ZTE Corporation, Sanechips |
| R2-2408534 |
Initialization of DRX_SFN_COUNTER at handover |
ZTE Corporation, Sanechips |
| R2-2408676 |
stage 2 Correction on additional buffer size table |
NEC, Nokia (Rapporteur) |
| R2-2408798 |
Correction to multi-PUSCH configured grant. |
Huawei, HiSilicon |
| R2-2408917 |
DRX SFN counter initialization |
Ericsson |
| R2-2408919 |
Corrections to Stage-2 for XR awareness |
Ericsson |
| R2-2408987 |
Corrections for delay-critical indication from PDCP to RLC |
Samsung |
| R2-2409014 |
Remaining issue on SFN COUNTER initiation for HO |
Nokia, Nokia Shanghai Bell |
| R2-2409015 |
Correction on DRX_SFN_COUNTER initiation at HO |
Nokia, Nokia Shanghai Bell |
| R2-2409381 |
stage 2 Correction on additional buffer size table |
NEC, Nokia (Rapporteur) |
| 7.6.1 |
Organizational |
|
| R2-2407910 |
LS on Rel-18 RAN1 UE features list for LTE after RAN1#118 (R1-2407390; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2408342 |
Miscellaneous corrections to TS 36.331 for IoT NTN |
Huawei, HiSilicon |
| R2-2408901 |
Applicability of optional UE Capabilities without signalling for NB-IoT |
Qualcomm Inc. |
| R2-2409178 |
IoT NTN Stage 2 correction |
Ericsson (Rapporteur) |
| R2-2409232 |
Applicability of optional UE Capabilities without signalling for NB-IoT |
Qualcomm Inc. |
| 7.6.2 |
Corrections |
|
| R2-2407967 |
Corrections on location based measurements and need code for IoT NTN |
CATT |
| R2-2408010 |
Corrections on CHO and measurement |
Huawei, HiSilicon |
| R2-2408011 |
Correction on UE Location Information Reporting in IoT-NTN |
vivo, Ericsson |
| R2-2408336 |
SIB33 related RRC corrections for IoT NT |
ZTE Corporation, Sanechips |
| R2-2408588 |
Discussion on satelliteId |
Apple |
| R2-2408589 |
Correction on satelliteId in SIB3/SIB5 |
Apple |
| R2-2408648 |
Enabling SystemInformationBlockType33 for NB-IoT NTN |
Google |
| R2-2408801 |
Various corrections for IoT NTN Rel-18 |
Samsung |
| R2-2408830 |
UE capabilities update for GNSS position fix in IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2409185 |
IoT NTN UE capabilities correction for GNSS and HARQ enhancements |
Ericsson |
| R2-2409233 |
Corrections on location based measurements and need code for IoT NTN |
CATT |
| R2-2409234 |
IoT NTN UE capabilities correction for GNSS and HARQ enhancements |
Ericsson |
| R2-2409235 |
Corrections on distance-based measurements during T-Service for IoT NTN |
Samsung |
| R2-2409236 |
Corrections on CHO and measurement |
Huawei, HiSilicon |
| R2-2409241 |
Corrections on CHO and measurement |
Huawei, HiSilicon |
| 7.7.1 |
Organizational |
|
| R2-2407912 |
LS on FR2-NTN inclusion to specifications (R1-2407406; contact: vivo) |
RAN1 |
| R2-2408012 |
Remaining Issues on FR2-NTN Support |
vivo |
| R2-2409186 |
Clarification of reference location within the MO for NR NTN Rel-18 |
Ericsson |
| 7.7.2 |
Corrections |
|
| R2-2407968 |
Correction on coexistence between CHO and satellite switching with re-synchronization |
CATT |
| R2-2408013 |
Correction on RACH-less HO in NR-NTN |
vivo, THALES |
| R2-2408341 |
Correction to satellite switch with resync |
Huawei, HiSilicon |
| R2-2408414 |
Correction on nr-NTN-MeasAndReport |
NEC Corporation. |
| R2-2408567 |
Clarification on TN to NTN mobility |
Apple, Qualcomm Incorporated |
| R2-2408654 |
Miscellaneous corrections on NTN in FR2 bands |
ZTE Corporation, Sanechips |
| R2-2408943 |
Correction to DL-DataToUL-ACK for NTN |
Nokia |
| R2-2408944 |
FR2-related Release 18 NTN Issues |
Nokia |
| R2-2409027 |
Miscellaneous corrections to NR NTN |
Samsung |
| R2-2409056 |
Correction on skipping TN measurements |
SHARP Corporation |
| R2-2409187 |
Remaining open issues |
Ericsson |
| R2-2409204 |
Correction to satellite switch with resync |
Huawei, HiSilicon |
| R2-2409244 |
Miscellaneous corrections to NR NTN |
Samsung |
| 7.9.2 |
Stage 2 corrections |
|
| R2-2408603 |
Miscellaneous corrections for SL relay |
ZTE Corporation, Sanechips |
| R2-2408611 |
draft_(Rel-18)_R2-38.300 relay stage 2 CR_rapp |
LG Electronics Inc. |
| R2-2408861 |
Correction on NR SL Multi-path relay operation |
Philips International B.V. |
| R2-2408879 |
U2U Relays, Local ID Assignment |
Ericsson |
| R2-2409094 |
draft_(Rel-18)_R2-38.300 relay stage 2 CR_rapp |
LG Electronics Inc. |
| R2-2409265 |
Miscellaneous and editorial changes for NR sidelink relay enhancement |
LG Electronics, ZTE Corporation, Sanechips, Philips International B.V. |
| R2-2409266 |
Miscellaneous and editorial changes for NR sidelink relay enhancement |
LG Electronics, ZTE Corporation, Sanechips, Philips International B.V. |
| 7.9.3 |
Control plane corrections (including UE capabilities) |
|
| R2-2408256 |
Miscellaneous CR for Rel-18 SL relay enhancement |
Huawei, HiSilicon |
| R2-2408584 |
Corrections on RRC SRAP configuration for L2 U2U |
Apple |
| R2-2408604 |
Corrections for U2U relay measurements |
ZTE Corporation, Sanechips |
| R2-2408862 |
RRC correction on NR SL U2U relay operation |
Philips International B.V. |
| R2-2409068 |
Correction on sl-SFN-DFN-Offset or sl-PagingInfo-RemoteUE release |
Google |
| R2-2409118 |
Clarification for ul-DataSplitThreshold setting in multi-path relay |
OPPO |
| R2-2409262 |
Miscellaneous CR for Rel-18 SL relay enhancement |
Huawei, HiSilicon |
| R2-2409263 |
RRC correction on NR SL U2U relay operation |
Philips International B.V. |
| 7.9.4 |
User plane corrections (including SRAP) |
|
| R2-2408374 |
Corrections on security for L2 U2U relay |
vivo |
| R2-2408662 |
Correction to error handling for U2U operation |
Huawei, HiSilicon |
| R2-2408880 |
PC5/Uu Relay RLC Channel Definition |
Ericsson |
| R2-2408936 |
Discussion on RLC channel Definition alignment across the specs |
Huawei, HiSilicon |
| R2-2409264 |
Correction to error handling for U2U operation |
Huawei, HiSilicon |
| 7.11.1 |
Organizational |
|
| R2-2408113 |
Rapporteur correction on the terminology of multicast MCCH |
Huawei, HiSilicon, Samsung |
| R2-2409389 |
Rapporteur correction on multicast MCCH |
Huawei, HiSilicon, Samsung, CATT |
| 7.11.2 |
Corrections |
|
| R2-2407995 |
Correction on Multicast MCCH Information Acquisition |
CATT,CBN |
| R2-2408112 |
Correction on multicast reception in RRC_INACTIVE upon paging |
Huawei, HiSilicon, Nokia, CATT, Ericsson, Samsung, Apple, ZTE |
| R2-2408242 |
Miscellaneous correction on eMBS |
SHARP Corporation |
| R2-2408407 |
Conflicts between legacy and enhanced group paging |
ZTE Corporation, Sanechips |
| R2-2408757 |
Corrections for MII |
Samsung |
| R2-2409057 |
Validity of PTM configuration in RRCRelease |
Ericsson |
| R2-2409085 |
Details of multicast reception in RRC_INACTIVE |
Nokia |
| R2-2409275 |
Paging clarification for MBS |
Sharp |
| R2-2409276 |
Clarification on MII usage |
Samsung |
| R2-2409277 |
Clarification on MII usage |
Samsung |
| R2-2409278 |
Clarification on MII usage |
Samsung |
| R2-2409279 |
Clarification on MII usage |
Samsung |
| R2-2409388 |
Correction on multicast reception in RRC_INACTIVE upon paging |
Huawei, HiSilicon, Nokia, CATT, Ericsson, Samsung, Apple, ZTE |
| 7.13.1 |
Organizational |
|
| R2-2408842 |
Miscellaneous corrections on R18 SONMDT for 36.331 |
Huawei, HiSilicon |
| 7.13.2 |
Corrections |
|
| R2-2408197 |
Miscellaneous corrections for Rel-18 SON/MDT |
CATT |
| R2-2408434 |
Corrections on SPR determination |
Samsung |
| R2-2408440 |
Correction on UE behavior of setting failedPSCellId |
NTTDOCOMO, INC. |
| R2-2408441 |
Correction on UE behavior of setting failedPSCellId |
NTTDOCOMO, INC. |
| R2-2408457 |
Correction on SPR content determination |
Google |
| R2-2408823 |
Removing Editor’s note on Fast MCG Recovery Failure Cause |
Ericsson |
| R2-2408843 |
Correction on setting CAPC related parameters in SCGFailureInformation message |
Huawei, HiSilicon |
| R2-2409281 |
Miscellaneous corrections for Rel-18 SON/MDT |
CATT |
| 7.14.1 |
Organizational |
|
| R2-2407923 |
LS on MBS Communication Service Type (R3-244789; contact: Ericsson) |
RAN3 |
| R2-2408745 |
Correction of Enhancement on NR QoE management and optimizations for diverse services |
Ericsson |
| 7.14.2 |
Corrections |
|
| R2-2408658 |
Consideration on QoE configuration release during inter-RAT mobility |
ZTE Corporation, Sanechips |
| R2-2408746 |
Discussion on IRAT handover from LTE |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2408833 |
Correction on QoE measurements release at successful handover from LTE/5GC to NR |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2408841 |
Correction on priority-based QoE measurements in TS 38.300 |
Huawei, HiSilicon |
| R2-2409274 |
Correction on priority-based QoE measurements in TS 38.300 |
Huawei, HiSilicon, China Unicom, Nokia, Ericsson, ZTE, Apple |
| 7.15.2 |
Corrections |
|
| R2-2407969 |
Correction on selection of resources for MCSt |
CATT, CICTCI |
| R2-2407972 |
Co-configuration of random/partial-sensing resource selection and Co-Ex |
OPPO |
| R2-2408105 |
Discussion on MCSt correction |
vivo |
| R2-2408252 |
TP for SL enhancemen in TS 38.321 |
NEC Corporation |
| R2-2408363 |
Correction on carrier selection for SL evolution |
Huawei, HiSilicon, LG Electronics Inc. |
| R2-2408538 |
Clarification on single and multiple carrier selection |
ZTE Corporation |
| R2-2408637 |
Correction on Co-channel coexistence for LTE sidelink and NR sidelink |
LG Electronics Inc. |
| R2-2408638 |
Correction on MCSt |
LG Electronics Inc. |
| R2-2408643 |
Discussion on MAC correction for resource selection of MCSt |
LG Electronics Inc. |
| R2-2408686 |
Correction to MAC on LCH carrier mapping for sidelink |
Ericsson |
| R2-2409351 |
MAC correction for resource selection of MCSt |
LG |
| R2-2409371 |
Correction on MCSt |
LG Electronics Inc. |
| 7.17.1 |
Organizational |
|
| R2-2408854 |
Clarification of UE capability restrictions in MUSIM |
Ericsson |
| R2-2409224 |
Clarification of UE capability restrictions in MUSIM |
Ericsson |
| 7.17.2 |
Corrections |
|
| R2-2408029 |
Clarification for the initiation of the MUSIM proactive UAI after HO/CHO |
Huawei, HiSilicon |
| R2-2408403 |
Correction to the musim-AffectedBandsList and musim-AvoidedBandsList |
ZTE Corporation |
| R2-2409223 |
Correction to the musim-AffectedBandsList and musim-AvoidedBandsList |
ZTE Corporation |
| 7.20 |
NR MIMO evolution |
|
| R2-2408510 |
Clarification to the k value in STx2P PHR MAC CE |
Huawei, HiSilicon |
| 7.20.2 |
Corrections |
|
| R2-2408180 |
Correction on simultaneousU-TCI-UpdateListx |
CATT, Nokia |
| R2-2408352 |
Discussion on supporting 8Tx in MAC specification |
ASUSTeK |
| R2-2408748 |
Considerations on Remaining UP Issues for R18 MIMO |
ZTE Corporation |
| R2-2408912 |
Correction to SRS resources for UL full power transmission mode 2 |
Ericsson |
| R2-2409024 |
Correction on multi-entry PHR for MIMO STx2P multi-panel scheme |
Samsung |
| R2-2409092 |
Remaining issue on STx2P PHR |
LG Electronics Inc. |
| R2-2409141 |
Clarification on the k values in the STx2P PHR MAC CE |
Huawei, HiSilicon |
| R2-2409221 |
Report of [AT127bis][201][MIMOevo] PHR related aspects |
Samsung |
| 7.24.1 |
TEI proposals by Other Groups |
|
| R2-2407905 |
Reply LS on Mitigation of Downgrade attacks (C1-245048; contact: vivo) |
CT1 |
| R2-2407971 |
Discussion on LS R4-2410693 |
OPPO |
| R2-2408401 |
Consideration on the intra-band EN-DC Channel Spacing |
ZTE Corporation |
| R2-2408473 |
Discussion on intra-band EN-DC channel spacing |
Huawei, HiSilicon |
| R2-2408474 |
Introduction of new capability for intra-band EN-DC channel spacing [Intra-Band_EN-DC_Channelspacing] |
Huawei, HiSilicon |
| R2-2408475 |
Introduction of new capability for intra-band EN-DC channel spacing [Intra-Band_EN-DC_Channelspacing] |
Huawei, HiSilicon |
| R2-2409399 |
Introduction of new capability for intra-band EN-DC channel spacing [Intra-Band_EN-DC_Channelspacing] |
Huawei, HiSilicon |
| 7.24.2.1 |
2Rx XR |
|
| R2-2408733 |
Correction for cell barring for 2Rx XR UE [2Rx_XR_Device] |
Huawei, HiSilicon, Xiaomi, Ericsson, LGE, ZTE Corporation |
| R2-2408881 |
Correction on 2RxXR and Aerial UEs |
Ericsson |
| 7.24.2.2 |
Other RAN2 TEI-18 |
|
| R2-2407922 |
Reply LS on Support of Emergency Calls for (e)Redcap UEs in barred cells (R3-244788; contact: Nokia) |
RAN3 |
| R2-2408128 |
Correction on barring exemption for (e)Redcap and XR 2RX UEs |
vivo, Guangdong Genius, Apple |
| R2-2408293 |
Discussion on the cell barring across R18 features |
Huawei, HiSilicon, Samsung |
| R2-2408368 |
Discussion on cell barring and associated behaviour |
Qualcomm Incorporated, Ericsson |
| R2-2408369 |
Clarifications on cell barring and cell reservation |
Qualcomm Incorporated, Ericsson |
| R2-2408370 |
Clarifications on cell barring and cell reservation |
Qualcomm Incorporated, Ericsson |
| R2-2408408 |
Search space configuration for RedCap UE’s MBS broadcast reception |
ZTE Corporation, Sanechips |
| R2-2408462 |
Coexistence issue for NES and NCR |
LG Uplus, SK Telecom, Telecom Italia, NTT Docomo, China Unicom, ETRI |
| R2-2408661 |
SIB1 processing correction for (e)RedCap and 2Rx XR UEs [EM_Call_Exemption] |
Nokia |
| R2-2408732 |
Correction for Paging monitoring during SDT [CG-SDT-Enh] |
Huawei, HiSilicon |
| R2-2409410 |
Summary of offline discussion [AT127bis][009][Cell Barring] behaviour (Qualcomm) |
Qualcomm Incorporated |
| 7.25.1 |
RAN4 led items |
|
| R2-2407930 |
LS on measurements without gap (R4-2413936; contact: Nokia) |
RAN4 |
| R2-2408212 |
Discussion on early implementation of UE capability on measurements gap enhancement (LS R4-2413936) |
CATT |
| R2-2408249 |
Corrections on the Need Code |
vivo |
| R2-2408388 |
On ATG timing advance reporting procedure |
Ericsson |
| R2-2408399 |
Consideration on Supporting 3M Channel Bandwidth |
ZTE Corporation |
| R2-2408400 |
Clarification on the Channel Bandwidth for the 3M |
ZTE Corporation |
| R2-2408444 |
Clarification of offsetThresholdTA-r18 for NR ATG |
Huawei, HiSilicon, CMCC, CATT, Nokia, Nokia Shanghai Bell |
| R2-2408480 |
Correction on BWP operation without bandwidth restriction |
Huawei, HiSilicon |
| R2-2408807 |
Clarification on Timing Advance Report MAC CE for ATG |
Samsung, Qualcomm, Huawei, HiSilicon, CMCC, CATT |
| R2-2408808 |
Correction on SCS applied for ATG offsetThreshold |
Samsung |
| R2-2408840 |
Correction to TS 38.306 for HST FR2 |
Huawei, HiSilicon |
| R2-2408975 |
Discussion on early implementation of R18 measurement gap enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2408976 |
Supporting R17 early implementation of R18 measurement gap enhancements |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, BT Plc., Telecom Italia, CATT |
| R2-2408977 |
Supporting R17 early implementation of R18 measurement gap enhancements |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, BT Plc., Telecom Italia, CATT |
| R2-2409055 |
Correction on carrier bandwidth configuration for less than 5MHz |
Huawei, HiSilicon |
| R2-2409069 |
Clarification on the unit of offsetThresholdTA-r18 for ATG |
ZTE Corporation |
| R2-2409070 |
Clarification on Timing Advance filed in the Timing Advance Report MAC CE |
ZTE Corporation |
| R2-2409171 |
Clarification on capability for inter-frequency configuration for less than 5MHz |
Huawei, HiSilicon |
| R2-2409217 |
Correction on carrier bandwidth configuration for less than 5MHz |
Huawei, HiSilicon |
| R2-2409385 |
Clarification on capability for inter-frequency configuration for less than 5MHz |
Huawei, HiSilicon |
| R2-2409391 |
[DRAFT] LS on carrierBandwidth configuration for less-than-5MHz carriers |
Huawei, HiSilicon |
| R2-2409397 |
Report of [AT127bis][011][less5MHz] 331 CR (ZTE) |
ZTE |
| R2-2409398 |
Offline 014 on early implementation of R18 measurement gap enhancements |
Nokia (Rapporteur) |
| R2-2409408 |
Report of [AT127bis][013][ATG] CRs (Samsung) |
Samsung |
| R2-2409409 |
LS on carrierBandwidth configuration for less-than-5MHz carriers |
RAN2 |
| 7.25.2 |
RAN1 led items |
|
| R2-2407916 |
Reply LS on UL Tx switching (R1-2407505; contact: NTT DOCOMO) |
RAN1 |
| R2-2408665 |
Addition of UE capability for 1T-1T switching (TS38.331CR) |
Huawei, HiSilicon, NTT DOCOMO, INC. |
| R2-2408666 |
Addition of UE capability for 1T-1T switching (TS38.306CR) |
Huawei, HiSilicon, NTT DOCOMO, INC. |
| R2-2409072 |
Miscellaneous corrections on UE capability for multi-cell scheduling |
NTT DOCOMO INC. |
| R2-2409099 |
Discussion on the applicable BWP for certain RRC parameters for DCI format 0_3/1_3 |
Samsung |
| R2-2409100 |
Correction on the applicable BWP for certain RRC parameters for DCI format 0_3/1_3 |
Samsung |
| R2-2409403 |
Correction on UE capability for multi-carrier enhancements |
NTT DOCOMO, INC. |
| R2-2409404 |
Correction on UE capability for multi-carrier enhancements |
NTT DOCOMO, INC. |
| 8.0 |
General |
|
| R2-2407937 |
LS on Clarification regarding definition of 5G NR femto ownership (S3-243518; contact: Nokia) |
SA3 |
| R2-2407943 |
LS on Number of UEs in RRC_INACTIVE state with data transmission (S5-245138; contact: China Telecom) |
SA5 |
| R2-2408205 |
Discussion on the number of SDT UEs in RRC_INACTIVE state (LS S5-245138) |
CATT |
| R2-2408537 |
Number of UEs in RRC_INACTIVE with data transmission |
ZTE Corporation, Sanechips |
| R2-2408734 |
Discussion on the LS from SA5 on the number of UEs in RRC_INACTIVE state with data transmission |
Huawei, HiSilicon, China Telecom |
| R2-2408762 |
Regarding LS from SA5 on Number of UEs in RRC_INACTIVE state with data transmission |
Ericsson |
| R2-2409280 |
Reply to SA5 LS on Number of UEs in RRC_INACTIVE state with data transmission |
RAN2 |
| 8.1.1 |
Organizational |
|
| R2-2407933 |
LS on AIML data collection (RP-242389; contact: InterDigital) |
RAN |
| R2-2407941 |
LS reply on improved KPIs involving end-to-end data volume transfer time analytics (S5-244658; contact: Ericsson) |
SA5 |
| R2-2407942 |
LS reply on terminology definitions for AI-ML in NG-RAN (S5-244660; contact: NEC, Intel) |
SA5 |
| R2-2409164 |
Work plan for Rel.19 AI/ML for NR air interface |
Ericsson |
| 8.1.2.2 |
LCM for UE-sided model for Beam Management use case |
|
| R2-2407956 |
Other LCM for UE-sided model for Beam Management use case |
OPPO |
| R2-2408037 |
Discussion on LCM for UE-sided model for BM |
China Telecom |
| R2-2408076 |
Discussion on LCM for UE-sided model for BM |
CMCC |
| R2-2408141 |
Discussion on LCM for UE-sided Model for Beam Management Use Case |
Fujitsu |
| R2-2408175 |
Discussion on LCM for UE-sided model for Beam Management |
Spreadtrum Communications |
| R2-2408208 |
Discussion on LCM for UE-sided model for BM use case |
CATT |
| R2-2408222 |
Discussion on LCM for UE-sided model for Beam Management |
vivo |
| R2-2408251 |
Discussion on LCM for UE sided model |
NEC Corporation |
| R2-2408263 |
Discussion on LCM for UE-sided model for BM |
Xiaomi |
| R2-2408312 |
LCM for UE sided model in beam management |
Lenovo |
| R2-2408353 |
Discussion on LCM for UE-sided models |
ASUSTeK |
| R2-2408375 |
Discussion on LCM for UE-sided model for Beam Management use case |
TCL |
| R2-2408376 |
Further Discussion on LCM for UE side Model |
ZTE Corporation |
| R2-2408390 |
On LCM for UE-sided Models for Beam Management |
Qualcomm Incorporated |
| R2-2408456 |
Discussion on LCM for UE-sided model for BM |
Google |
| R2-2408484 |
Further Discussion on Functionality-based LCM for UE-side Model |
MediaTek Inc. |
| R2-2408553 |
LCM for UE-side Beam Management |
Nokia |
| R2-2408563 |
Remaining issues on LCM procedure of UE-sided model for AI/ML based beam management |
Apple |
| R2-2408705 |
Some aspects for model inference and model monitoring |
Sony |
| R2-2408735 |
Discussion on LCM for UE-sided model for Beam Management use case |
Huawei, HiSilicon |
| R2-2408921 |
Remaining details of applicable functionality reporting |
InterDigital |
| R2-2408931 |
On LCM for UE-sided Beam Management |
SHARP |
| R2-2408963 |
Disuccsion on LCM for UE-sided model for beam management |
Samsung |
| R2-2408999 |
Considerations on LCM of AI/ML for NR air Interface |
Kyocera |
| R2-2409038 |
LCM for UE-sided model for BM |
LG Electronics |
| R2-2409062 |
Discussion on LCM for UE-Side Model for Beam Management use case |
Futurewei Technologies |
| R2-2409103 |
LCM for UE-side models for beam management |
Ericsson |
| R2-2409107 |
Discussion on Functionality-based LCM of UE-sided Model for Beam Management Use Cases |
CEWiT |
| R2-2409166 |
Discussion on LCM for UE-side model for BM |
NTT DOCOMO, INC. |
| R2-2409393 |
[017] Report of Offline Discussion on LCM Definitions |
Nokia |
| 8.1.2.3 |
LCM for Positioning use case |
|
| R2-2407957 |
LCM for Positioning use case |
OPPO |
| R2-2408038 |
Discussion on LCM for positioning use case |
China Telecom |
| R2-2408098 |
Discussion on LCM for positioning |
CMCC |
| R2-2408142 |
Discussion on LCM for Positioning Use Case |
Fujitsu |
| R2-2408209 |
Consideration on LCM for Positioning use case |
CATT |
| R2-2408218 |
Discussion on LCM for positioning use case |
ZTE Corporation |
| R2-2408223 |
Discussion on functionality LCM for AI/ML enhanced positioning |
vivo |
| R2-2408313 |
LCM for AIML based positioning with UE-sided model |
Lenovo |
| R2-2408505 |
Lifecycle management for positioning use-cases |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2408527 |
Discussion on LCM for Positioning use case |
Samsung |
| R2-2408543 |
LCM for positioning use case |
Qualcomm Incorporated |
| R2-2408548 |
LCM for Positioning use case |
NEC |
| R2-2408554 |
LCM for UE-side Positioning |
Nokia |
| R2-2408564 |
LCM procedure of AI/ML based positioning |
Apple |
| R2-2408618 |
Discussion on LCM for UE sided model for AI positioning |
Xiaomi |
| R2-2408725 |
Support for AI/ML for positioning accuracy enhancement |
Sony |
| R2-2408837 |
Discussion on LCM for Positioning use case |
Huawei, HiSilicon |
| R2-2408922 |
LCM for Positioning |
Interdigital Inc. |
| R2-2408932 |
LCM For Positioning |
Ericsson |
| R2-2408941 |
LCM for Positioning use case |
AT&T Services, Inc. |
| R2-2409108 |
Discussion on Functionality-based LCM for Positioning Use Case |
CEWiT |
| R2-2409396 |
Offline on LCM for positioning |
InterDigital Inc. (Rapporteur) |
| 8.1.3 |
NW side data collection |
|
| R2-2407958 |
Data Collection for Network Side Model Training |
OPPO |
| R2-2408039 |
Discussion on NW-side data collection for AI/ML based beam management |
China Telecom |
| R2-2408077 |
Discussion on NW side data collection |
CMCC |
| R2-2408143 |
Discussion on NW side Data Collection for Beam Management |
Fujitsu |
| R2-2408144 |
Discussion on NW side Data Collection for Positioning |
Fujitsu |
| R2-2408176 |
Discussion on NW-side data collection |
Spreadtrum Communications |
| R2-2408210 |
Consideration on NW side data collection |
CATT |
| R2-2408224 |
Discussion on NW side data collection framework |
vivo |
| R2-2408264 |
Discussion on NW side data collection |
Xiaomi |
| R2-2408314 |
Data Collection for NW-sided model training in beam management |
Lenovo |
| R2-2408315 |
Data Collection for NW-sided model training in positioning |
Lenovo |
| R2-2408377 |
Further Consideration on NW side Data Collection |
ZTE Corporation |
| R2-2408391 |
On Network Side Data Collection |
Qualcomm Incorporated |
| R2-2408418 |
AIML MDT-based data collection for NW-side model |
NEC |
| R2-2408485 |
Enhanced MDT for Data collection for Network Side Model Training |
MediaTek (Hefei) Inc. |
| R2-2408544 |
Data Collection for NW-side models |
Nokia |
| R2-2408565 |
Further discussion on NW-sided data collection |
Apple |
| R2-2408615 |
Disuccsion on NW side data collection |
Samsung |
| R2-2408634 |
Discussion on Data Collection for NW-side Model |
SHARP Corporation |
| R2-2408670 |
Discussion on NW side data collection for positioning |
TCL |
| R2-2408838 |
Discussion on NW-sided data collection for training |
Huawei, HiSilicon |
| R2-2408923 |
Data Collection for Network-Sided Model Training for the beam management use case |
Interdigital Inc. |
| R2-2409039 |
NW side data collection |
LG Electronics |
| R2-2409063 |
Discussion on Data Collection for NW-side Model Training |
Futurewei Technologies |
| R2-2409162 |
NW-side data collection for beam management and positioning |
Ericsson |
| 8.1.5 |
Model transfer/delivery |
|
| R2-2407959 |
Further analysis on Model Transfer/Delivery |
OPPO |
| R2-2408031 |
AI/ML model transfer |
Xiaomi |
| R2-2408040 |
Discussion on model transfer/delivery |
China Telecom |
| R2-2408078 |
Discussion on AIML model transfer delivery |
CMCC |
| R2-2408211 |
AI/ML model transfer/delivery |
CATT |
| R2-2408225 |
Further analysis of model transfer/delivery |
vivo |
| R2-2408378 |
Consideration on Model Transfer and delivery in RAN2 |
ZTE Corporation |
| R2-2408392 |
Discussion on Model Delivery/Transfer |
Qualcomm Incorporated |
| R2-2408486 |
Further Analysis on Model Transfer/Delivery Solutions |
MediaTek (Hefei) Inc. |
| R2-2408552 |
AIML Model Transfer |
NEC |
| R2-2408555 |
Model transfer/delivery |
Nokia |
| R2-2408566 |
Discussion on Model transfer / delivery |
Apple |
| R2-2408691 |
Downselection of the AI_ML model delivery options |
BT plc |
| R2-2408839 |
Discussion on model transfer and delivery |
Huawei, HiSilicon |
| R2-2408924 |
Model transfer/delivery |
Interdigital Inc. |
| R2-2409040 |
Model transfer delivery |
LG Electronics |
| R2-2409067 |
Discussion on model transfer/delivery |
Futurewei Technologies |
| R2-2409154 |
Model transfer/delivery: key issues and way forward for RAN2 |
Samsung R&D Institute UK |
| R2-2409165 |
On model transfer/delivery |
Ericsson |
| 8.2.1 |
Organizational |
|
| R2-2407907 |
Reply LS on Clarification of requirements for Ambient IoT (R1-2407364; contact: Ericsson) |
RAN1 |
| R2-2407934 |
Reply LS on Clarification of requirements for Ambient IoT (S1-242527; contact: Ericsson) |
SA1 |
| R2-2407984 |
TP for TR 38.769 update |
Huawei, CMCC, T-Mobile USA |
| R2-2409405 |
Reply LS to RAN2 on data block sizes for Ambient IoT (R1-2409250; contact: MediaTek) |
RAN1 |
| 8.2.2 |
Functionality aspects |
|
| R2-2407946 |
Discussion on the Functionality Aspects for Ambient IoT |
CATT |
| R2-2408058 |
Ambient-IoT Functionality Aspects |
NEC Corporation |
| R2-2408099 |
Discussion on functionality for A-IoT |
CMCC |
| R2-2408145 |
Discussions on Functionality Aspect of Ambient IoT |
Fujitsu |
| R2-2408166 |
Discussion on the functionalities required for Ambient IoT |
Spreadtrum Communications |
| R2-2408191 |
Discussion on A-IOT functionality aspects |
Xiaomi |
| R2-2408226 |
Discussion on functionality aspects for Ambient IoT |
vivo |
| R2-2408253 |
A-IoT functionalities |
Huawei, HiSilicon |
| R2-2408275 |
Discussions on A-IoT functionality |
HONOR |
| R2-2408291 |
Stop-and-wait protocol for UP |
ZTE Corporation, Sanechips, China Unicom, Nordic Semiconductor ASA |
| R2-2408355 |
Discussion on energy status report and data status indication |
ASUSTeK |
| R2-2408395 |
Functionality for Ambient IOT |
InterDigital |
| R2-2408446 |
Energy Status report |
Vodafone, Qualcomm, Nokia, Interdigital, Xiaomi, Samsung, Deutsche Telekom, ZTE, Sharp, Semtech, Asustek |
| R2-2408448 |
Discussion on AIoT functionalities |
OPPO |
| R2-2408449 |
Discussion on AIoT functionalities |
OPPO |
| R2-2408453 |
Inventory procedure without device ID |
Vodafone |
| R2-2408458 |
Discussion on Ambient IoT device AS ID and device energy status report |
Panasonic |
| R2-2408482 |
Discussion on A-IoT functionality |
ETRI |
| R2-2408504 |
AIoT Functionality Aspects |
Nokia France |
| R2-2408542 |
Energy status report for Ambient-IoT |
Quectel |
| R2-2408546 |
Considerations on functionality aspects for Ambient IoT |
Lenovo |
| R2-2408580 |
Functional Aspects of Ambient IoT |
Apple |
| R2-2408668 |
Functionality aspects for A-IoT |
Ericsson |
| R2-2408671 |
Discussions on Energy Status Report in Ambient IoT Devices |
ROBERT BOSCH GmbH |
| R2-2408701 |
Discussion on A-IoT functionalities |
NTT DOCOMO INC. |
| R2-2408706 |
Considerations on functionality aspects for Ambient IoT |
Sony |
| R2-2408829 |
Discussion on functionality for ambient IoT |
Google Ireland Limited |
| R2-2408850 |
Discussion on Functionalities Required for A-IoT |
China Telecom |
| R2-2408934 |
Message size reporting and segmentation |
Nordic Semiconductor ASA |
| R2-2408942 |
Considerations for energy status report |
Semtech Neuchatel SA |
| R2-2408952 |
Ambient IoT data transmission after initial access |
MediaTek Inc. |
| R2-2408955 |
Use cases for energy status report in AIoT |
SHARP Corporation |
| R2-2408993 |
Further consideration of functionality aspects for Ambient IoT |
Kyocera |
| R2-2409013 |
Discussino on segmentation functionalities for Ambient IoT |
Samsung Electronics Czech |
| R2-2409021 |
Views on Functionality Aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2409022 |
Discussions on functionalities required for AIoT |
Samsung Electronics Czech |
| R2-2409029 |
Discussion on functionality aspects of ambient IoT |
LG Electronics Inc. |
| R2-2409114 |
Segementation for AIoT |
Wiliot Ltd. |
| R2-2409172 |
Discussions on AS ID for Ambient IoT devices |
Futurewei |
| R2-2409412 |
LS on assistance information from the CN to the Reader for A-IoT |
RAN2 |
| 8.2.3 |
A-IoT Paging |
|
| R2-2407947 |
Discussion on Paging for Ambient IoT |
CATT |
| R2-2407954 |
Discussion on A-IOT paging procedure |
Xiaomi |
| R2-2408059 |
Discussion on the paging for A-IoT |
Transsion Holdings |
| R2-2408068 |
Discussion on A-IoT paging |
CMCC |
| R2-2408137 |
Discussion on paging procedure for Ambient IoT |
OPPO |
| R2-2408146 |
Discussions on AIoT paging |
Fujitsu |
| R2-2408162 |
Ambient-IoT Paging |
NEC |
| R2-2408170 |
Discussion on paging procedure of A-IoT |
Spreadtrum Communications |
| R2-2408186 |
Discussion on ambient IoT paging |
LG Electronics Inc. |
| R2-2408227 |
Discussion on AIoT Paging |
vivo |
| R2-2408254 |
A-IoT paging |
Huawei, HiSilicon |
| R2-2408278 |
Discussion on A-IoT paging |
HONOR |
| R2-2408309 |
Discussion on paging procedure for Ambient IoT |
Lenovo |
| R2-2408331 |
Further consideration on the details of paging for AIoT |
ZTE Corporation, Sanechips |
| R2-2408356 |
Discussion on Ambient IoT paging message with multiple IDs |
ASUSTeK |
| R2-2408396 |
Paging Related Aspects for Ambient IOT |
InterDigital |
| R2-2408439 |
Ambient IoT device paging |
TCL |
| R2-2408463 |
Discussion on A-IoT paging |
Panasonic |
| R2-2408581 |
Discussion on Ambient IoT Paging |
Apple |
| R2-2408625 |
Ambient IoT Paging |
Qualcomm Incorporated |
| R2-2408698 |
Paging procedures for Ambient IoT |
Nokia |
| R2-2408702 |
Discussion on A-IoT paging message |
NTT DOCOMO INC. |
| R2-2408707 |
Considerations on paging for Ambient IoT |
Sony |
| R2-2408847 |
Ambient IoT Paging Procedure |
China Telecom |
| R2-2408848 |
Ambient IoT Paging Procedure |
China Telecom |
| R2-2408869 |
Discussion on A-IoT paging |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2408906 |
Discussion on Paging aspects for Ambient-IoT |
Continental Automotive |
| R2-2408951 |
Ambient IoT paging and unification of use cases |
MediaTek Inc. |
| R2-2408954 |
Duplicate A-IoT paging message transmission and indication |
SHARP Corporation |
| R2-2408961 |
Discussion on DL messages for Ambient IoT UEs |
Ericsson |
| R2-2408992 |
Further consideration of A-IoT paging for Ambient IoT |
Kyocera |
| R2-2409019 |
Discussion on A-IoT paging |
Samsung Electronics Czech |
| R2-2409050 |
Discussion on Ambient IoT paging |
LG Uplus |
| R2-2409109 |
Discussion on A-IOT paging procedure |
CEWiT |
| R2-2409176 |
Further discussions on Ambient IoT Paging |
Futurewei |
| 8.2.4 |
A-IoT Random Access |
|
| R2-2407948 |
Discussion on the Random Access for Ambient IoT |
CATT |
| R2-2407953 |
Discussion on access procedure for ambient IOT |
Xiaomi |
| R2-2407985 |
Report of [POST127][033][AIoT] Random Access |
Huawei, HiSilicon |
| R2-2408041 |
Discussion on A-IoT random access |
China Telecom |
| R2-2408060 |
Discussion on the random access for A-IoT |
Transsion Holdings |
| R2-2408093 |
Further consideration on random access for ambient IoT |
CMCC |
| R2-2408140 |
random access for AIoT |
OPPO |
| R2-2408147 |
Discussions on AIoT Random Access |
Fujitsu |
| R2-2408167 |
Discussion on random access of Ambient IoT |
Spreadtrum Communications |
| R2-2408192 |
Study the A-IoT random access procedure |
Tejas Network Limited |
| R2-2408228 |
Random Access Procedure for A-IoT Device |
vivo |
| R2-2408243 |
A-IoT random access procedure |
Huawei, HiSilicon |
| R2-2408277 |
Discussion on A-IoT random access |
HONOR |
| R2-2408310 |
Discussion on random access for Ambient IoT |
Lenovo |
| R2-2408383 |
Discussion on random access for AIoT |
China Unicom |
| R2-2408397 |
Random Access Procedure for Ambient IOT |
InterDigital |
| R2-2408512 |
Considerations for D2R failure/success indication in A-IoT |
Panasonic |
| R2-2408536 |
Unified random-access procedure for A-IoT |
ZTE Corporation, Sanechips |
| R2-2408549 |
Random Access for Ambient IoT device |
NEC |
| R2-2408582 |
Discussion on Random Access for Ambient IoT |
Apple |
| R2-2408672 |
Discussions on Failure Detection/Recovery in Ambient IoT Devices |
ROBERT BOSCH GmbH |
| R2-2408688 |
Discussion on UL multiple access |
Ericsson |
| R2-2408700 |
Discussion on random access for Ambient AIoT |
Nokia |
| R2-2408703 |
Discussion on A-IoT random access |
NTT DOCOMO INC. |
| R2-2408708 |
Considerations on random access aspects for Ambient IoT |
Sony |
| R2-2408834 |
Discussion on multiple access for ambient IoT |
Google Ireland Limited |
| R2-2408908 |
Discussion on RACH aspects for Ambient-IoT |
Continental Automotive |
| R2-2408927 |
Further discussions on A-IoT random access |
ETRI |
| R2-2408938 |
AS scheduling ID and AS short ID considerations |
Nordic Semiconductor ASA |
| R2-2408995 |
Discussion on random access of Ambient IoT |
Kyocera |
| R2-2409028 |
Views on Random Access Aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2409075 |
Discussion on Ambient IoT random access |
KT Corp. |
| R2-2409110 |
Discussion on random access for Ambient IoT |
CEWiT |
| R2-2409119 |
Random Access Ack/Nack |
Wiliot Ltd. |
| R2-2409122 |
Discussion on random access aspects for Ambient IoT |
LG Electronics Inc. |
| R2-2409167 |
Discussion on A-IOT RACH related aspects |
Rakuten Mobile, Inc |
| R2-2409169 |
Timing Relationship of Msg3 and R2D response |
Philips International B.V. |
| R2-2409173 |
Further discussions on Ambient IoT random access |
Futurewei |
| 8.2.5 |
Topology 2 considerations |
|
| R2-2407949 |
Discussion on Topology 2 for Ambient IoT |
CATT |
| R2-2408042 |
Discussion on Topology 2 related aspects for Ambient IoT |
China Telecom |
| R2-2408069 |
Discussions on topology 2 for A-IoT |
CMCC |
| R2-2408139 |
Discussion on topology 2 for Ambient IOT |
OPPO |
| R2-2408148 |
Discussions on topology 2 related aspects |
Fujitsu |
| R2-2408171 |
Discussion on Topology 2 issues |
Spreadtrum Communications |
| R2-2408188 |
Considerations on TP2 related aspects between BS and UE reader |
Beijing Xiaomi Software Tech |
| R2-2408195 |
Discussion on Topology 2 for A-IoT |
SHARP Corporation |
| R2-2408229 |
Discussion on Topology 2 related aspects |
vivo |
| R2-2408255 |
A-IoT Topology 2 aspects |
Huawei, HiSilicon |
| R2-2408276 |
Consideration on resource allocation for Topology 2 |
HONOR |
| R2-2408311 |
Considerations on Topology 2 for Ambient IoT |
Lenovo |
| R2-2408332 |
Further consideration on TP2 for AIoT |
ZTE Corporation, Sanechips |
| R2-2408357 |
Consideration on information and scenario in Topology 2 |
ASUSTeK |
| R2-2408398 |
Topology 2 for Ambient IOT |
InterDigital |
| R2-2408583 |
Discussion on Ambient IoT Topology 2 |
Apple |
| R2-2408609 |
Topology 2 related aspects |
NEC |
| R2-2408626 |
Further aspects of Topology 2 |
Qualcomm Incorporated |
| R2-2408687 |
On Topology 2 and DO-A |
Ericsson |
| R2-2408753 |
Toplogy 2 considerations |
Nokia |
| R2-2408868 |
Considerations on Topology 2 for Ambient IoT |
TCL |
| R2-2408953 |
Ambient IoT topology 2 and out-of-coverage operation |
MediaTek Inc. |
| R2-2408994 |
Discussion on Topology 2 aspects of Ambient IoT |
Kyocera |
| R2-2409020 |
Discussion on A-IoT Topology 2 |
Samsung Electronics Czech |
| R2-2409030 |
Discussion on topology 2 considerations of ambient IoT |
LG Electronics Inc. |
| 8.3.1 |
Organizational |
|
| R2-2407975 |
Revised work plan of AI Mobility SI |
OPPO |
| R2-2407976 |
Text proposal of 38.744 |
OPPO |
| R2-2409011 |
Text proposal on TR 38.744 |
OPPO |
| R2-2409194 |
Revised work plan of AI Mobility SI |
OPPO, MediaTek, Nokia |
| R2-2409402 |
Discussion on work plan and potential SLS |
OPPO |
| 8.3.2 |
RRM measurement prediction |
|
| R2-2407977 |
Discussion on simulation result of RRM measurement |
OPPO |
| R2-2407979 |
Simulation results for RRM measurement prediction |
vivo |
| R2-2408073 |
Simulation results for RRM measurement prediction |
CMCC |
| R2-2408174 |
Simulation results and other aspects on RRM measurement prediction |
Spreadtrum Communications, BUPT |
| R2-2408206 |
Simulation results of RRM Measurement Prediction |
CATT, Turkcell |
| R2-2408265 |
Discussion on RRM prediction |
Xiaomi |
| R2-2408326 |
Discussions and evaluations on RRM measurement prediction |
NTT DOCOMO, INC. |
| R2-2408358 |
Discussion on other aspects related to RRM measurement prediction |
ASUSTeK |
| R2-2408393 |
Simulation results for RRM measurement prediction |
Qualcomm Incorporated |
| R2-2408419 |
Discussion on some clarification for RRM measurement prediction |
NEC |
| R2-2408438 |
AI/ML RRM measurement prediction |
TCL |
| R2-2408442 |
Discussion on cluster based RRM measurement prediction for high speed railway communications |
BJTU |
| R2-2408483 |
Report of [POST127][027][AI Mob] Simulation table (Mediatek) |
MediaTek Inc. |
| R2-2408487 |
RRM measurement prediction |
Lenovo |
| R2-2408520 |
Evaluation on RRM measurement prediction |
ZTE Corporation |
| R2-2408529 |
Discussion on RRM measurement prediction |
Samsung |
| R2-2408556 |
RRM measurement prediction results using field and simulated data |
Apple Inc |
| R2-2408558 |
Evaluation and Simulation Results for AIML RRM Prediction |
MediaTek Inc. |
| R2-2408736 |
Simulation results and discussion on RRM measurement prediction |
Huawei, HiSilicon |
| R2-2408740 |
AI/ML RRM measurement prediction |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2408747 |
Simulation results for temporal and inter-frequency RRM measurement predictions |
Ericsson |
| R2-2408872 |
AI-ML based Inter-frequency measurement prediction |
Rakuten Mobile, Inc |
| R2-2408925 |
Simulation results for RRM measurement predictions |
Interdigital Inc. |
| R2-2408929 |
RRM Measurement Prediction Evaluation Results |
Nokia |
| R2-2408967 |
Discussion on RRM Measurement Prediction Framework |
Meta |
| R2-2408974 |
Discussion on RRM measurement prediction |
ETRI |
| R2-2409188 |
Simulation results for RRM Measurement Prediction |
CEWiT |
| R2-2409201 |
RRM measurement prediction results using field and simulated data |
Apple Inc |
| R2-2409203 |
Simulation results and discussion on RRM measurement prediction |
Huawei, HiSilicon |
| R2-2409207 |
Evaluation on RRM measurement prediction |
ZTE Corporation |
| R2-2409407 |
[AT127bis][016][AI Mob] Simulation table example (Mediatek) |
Mediatek Inc. |
| R2-2409413 |
[POST127bis][016][AI Mob] Simulation results (Mediatek) |
MediaTek Inc. |
| 8.3.3 |
Measurement event predictions |
|
| R2-2407978 |
Discussion on measurement event prediction |
OPPO |
| R2-2407980 |
Discussion on measurement event prediction |
vivo |
| R2-2408032 |
Measurement event prediction |
Xiaomi |
| R2-2408079 |
Discussion on measurement event prediction |
CMCC |
| R2-2408207 |
Discussion on Measurement Event Prediction |
CATT, Turkcell |
| R2-2408298 |
Other Aspects for AI based Measurement Event Prediction |
Continental Automotive |
| R2-2408318 |
Discussion on measurement event prediction |
Lenovo |
| R2-2408327 |
Discussions on measurement event prediction |
NTT DOCOMO, INC. |
| R2-2408359 |
Discussion on measurement event prediction |
ASUSTeK |
| R2-2408394 |
Measurement Event prediction |
Qualcomm Incorporated |
| R2-2408431 |
Evaluation methodology, scenario and simulation assumption for measurement event prediction |
MediaTek (Chengdu) Inc. |
| R2-2408493 |
Discussion on measurement event prediction |
Jio |
| R2-2408521 |
Discussion on measurement event prediction |
ZTE Corporation |
| R2-2408551 |
Target scenarios for measurement event prediction |
NEC |
| R2-2408557 |
On Measurement Event Prediction Evaluation |
Apple Inc |
| R2-2408616 |
Discussion on measurement event prediction |
Samsung |
| R2-2408679 |
Discussion on measurement event predictions |
III |
| R2-2408737 |
Discussion on simulations for measurement event prediction |
Huawei, HiSilicon |
| R2-2408825 |
AI based measurement events prediction: Use cases, and simulations |
Ericsson |
| R2-2408926 |
Measurement event prediction |
Interdigital Inc. |
| R2-2408930 |
Discussion on Measurement Event Prediction |
Nokia |
| R2-2408978 |
Discussion on measurement event predictions |
ETRI |
| R2-2409066 |
Event prediction use cases and KPI |
LG Electronics Inc. |
| R2-2409095 |
Discussion on Measurement Event Predictions |
SHARP Corporation |
| 8.3.4 |
RLF/HO failure prediction |
|
| R2-2408874 |
AI-ML based RLF/HO failure prediction |
Rakuten Mobile, Inc |
| R2-2408968 |
Evaluation Assumptions for RLF/HO Failure Prediction |
Meta |
| R2-2409126 |
Discussion on simulation assumption for RLF prediction |
KDDI Corporation |
| 8.4.1 |
Organizational |
|
| R2-2407921 |
LS on LP-WUS operation in IDLE/INACTIVE mode (R1-2407559; contact: Apple) |
RAN1 |
| 8.4.2 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
|
| R2-2408007 |
Procedure and configuration of LP-WUS for IDLE and INACTIVE mode |
ZTE Corporation, Sanechips |
| R2-2408043 |
LP-WUS in RRC_IDLE and INACTIVE |
China Telecom |
| R2-2408072 |
LP-WUS operation in IDLE/INACTIVE modes |
CMCC |
| R2-2408114 |
Discussion on LP-WUS WUR in RRC_IDLE INACTIVE |
vivo |
| R2-2408168 |
Discussion on LP-WUS operation in IDLE/INACTIVE mode |
Spreadtrum Communications |
| R2-2408182 |
LP-WUS in RRC_IDLE/INACTIVE |
CATT |
| R2-2408239 |
Discussion on LP-WUS in RRC_IDLE and RRC_INACTIVE |
Sharp |
| R2-2408289 |
Procedure of LP-WUS in RRC_IDLE and INACTIVE |
HONOR |
| R2-2408415 |
Discussion on LP-WUS in RRC_IDLE INACTIVE |
NEC |
| R2-2408428 |
General considerations on the procedure for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2408447 |
Discussion on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Huawei, HiSilicon |
| R2-2408450 |
Discussion on procedure and configuration of LP-WUS in RRC_IDLEINACTIVE |
OPPO |
| R2-2408489 |
Procedure and Configuration of LP-WUS in RRC Idle/ Inactive |
Lenovo |
| R2-2408572 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Apple |
| R2-2408709 |
RAN2 aspects on LP-WUS/WUR in RRC Idle/Inactive mode |
Sony |
| R2-2408741 |
LP-WUS in IDLE and INACTIVE |
Nokia |
| R2-2408763 |
LP-WUS operation in IDLE/Inactive state |
Qualcomm Incorporated |
| R2-2408768 |
LP-WUS operation in RRC_IDLE and RRC_INACTIVE |
LG Electronics Inc. |
| R2-2408949 |
Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes |
InterDigital, Inc. |
| R2-2409005 |
Procedure and Configuration of LP-WUS in RRC Idle Inactive Mode |
Samsung |
| R2-2409058 |
LP-WUS in Idle and Inactive |
Ericsson |
| R2-2409157 |
On LR and MR operating frequencies (related to LS in R1-2407559) |
Vodafone |
| R2-2409222 |
[Draft]LS to on LP-WUS subgrouping |
vivo |
| R2-2409225 |
LS to on LP-WUS subgrouping |
RAN2 |
| R2-2409226 |
LS on LP-WUS subgrouping |
RAN2 |
| 8.4.3 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
|
| R2-2408008 |
RRM measurement relaxation and offloading in RRC_IDLE and RRC_INACTIVE mode |
ZTE Corporation, Sanechips |
| R2-2408071 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE INACTIVE |
CMCC |
| R2-2408111 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Huawei, HiSilicon |
| R2-2408115 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
vivo |
| R2-2408159 |
Discussion on RRM measurement in RRC IDLE and INACTIVE |
OPPO |
| R2-2408169 |
Discussion on RRM measurement relaxation in IDLE/INACTIVE mode |
Spreadtrum Communications |
| R2-2408183 |
RRM Relaxation and Offloading in RRC_IDLE/INACTIVE |
CATT |
| R2-2408240 |
Discussion on RRM measurement relaxation and offloading |
Sharp |
| R2-2408306 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Lenovo |
| R2-2408416 |
Discussion on LP-WUS RRM |
NEC |
| R2-2408429 |
Discussion on RRM measurement relaxation for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2408573 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Apple |
| R2-2408710 |
Discussion on RRM aspects for LP-WUS/WUR |
Sony |
| R2-2408742 |
RRM measurement relaxation in RRC_IDLE/INACTIVE |
Nokia |
| R2-2408765 |
LP-WUS RRM measurement relaxation and offloading |
Qualcomm Incorporated |
| R2-2408769 |
RRM relaxation and RRM offloading |
LG Electronics Inc. |
| R2-2408849 |
RRM Measurement Relaxation and Offloading in RRC_IDLE /INACTIVE Mode |
China Telecom |
| R2-2408950 |
Discussion on RRM measurement relaxation and offloading |
InterDigital, Inc. |
| R2-2409006 |
RRM measurement relaxation and offloading in RRC Idle Inactive Mode |
Samsung |
| R2-2409059 |
LP-WUS and RRM measurements |
Ericsson |
| 8.4.4 |
Procedures for LP-WUS in RRC_CONNECTED |
|
| R2-2408009 |
Procedures for LP-WUS in RRC_CONNECTED |
ZTE Corporation, Sanechips |
| R2-2408030 |
Discussion on LP-WUS for RRC_CONNECTED mode |
Huawei, HiSilicon |
| R2-2408044 |
Procedures for LP-WUS in RRC_CONNECTED |
China Telecom |
| R2-2408084 |
Discussion on LP-WUS operation in CONNECTED mode |
CMCC |
| R2-2408116 |
Discussion on LP-WUS WUR in RRC_Connected |
vivo |
| R2-2408184 |
Analysis on LP-WUS for RRC_CONNECTED Mode |
CATT |
| R2-2408290 |
Procedure of LP-WUS in RRC_CONNECTED |
HONOR |
| R2-2408417 |
Discussion on LP-WUS in RRC_CONNECTED |
NEC |
| R2-2408430 |
Discussing on LP-WUS monitoring for RRC_Connected |
Xiaomi Communications |
| R2-2408451 |
Discussion on LP-WUS in RRC_CONNECTED |
OPPO |
| R2-2408490 |
LP-WUS in RRC Connected Mode |
Lenovo |
| R2-2408574 |
Procedures for LP-WUS in RRC_CONNECTED |
Apple |
| R2-2408605 |
LP-WUS operation in RRC_CONNECTED Mode |
LG Electronics Inc. |
| R2-2408692 |
LP-WUS in CONNECTED mode |
InterDigital |
| R2-2408711 |
Considerations on LP-WUS/WUR in RRC Connected mode |
Sony |
| R2-2408764 |
LP-WUS operation in CONNECTED state |
Qualcomm Incorporated |
| R2-2409007 |
Procedures for LP-WUS in RRC Connected Mode |
Samsung |
| R2-2409052 |
Discussion on LP-WUS for CONNECTED state |
NTT DOCOMO INC. |
| R2-2409060 |
LP-WUS in Connected |
Ericsson |
| R2-2409076 |
LP-WUS in RRC_CONNECTED |
Nokia |
| R2-2409160 |
LP-WUS operation in RRC_CONNECTED Mode |
LG Electronics Inc. |
| 8.5.1 |
Organizational |
|
| R2-2407914 |
LS to RAN2 for on-demand SSB SCell operation (R1-2407438; contact: LGE) |
RAN1 |
| R2-2408559 |
Updated workplan for Rel-19 network energy savings WI |
Rapporteurs (Ericsson, Apple) |
| 8.5.2 |
On-demand SSB SCell operation |
|
| R2-2407973 |
Discussion on On-Demand SSB |
OPPO |
| R2-2407990 |
Consideration on on-demand SSB SCell operation |
CATT |
| R2-2408004 |
On-demand SSB SCell operation in connected mode |
ZTE Corporation, Sanechips |
| R2-2408045 |
Further consideration for on-demand SSB |
China Telecom |
| R2-2408085 |
Discussion on on-demand SSB |
CMCC |
| R2-2408100 |
Discussion on on-demand SSB SCell operation |
vivo |
| R2-2408172 |
Discussion on on-demand SSB Scell operation |
Spreadtrum Communications |
| R2-2408189 |
Discussion on on-demand SSB |
Xiaomi |
| R2-2408237 |
Discussion on on-demand SSB SCell operation for NES |
Huawei, HiSilicon |
| R2-2408295 |
On-demand SSB SCell Operation |
Samsung Electronics Co., Ltd |
| R2-2408321 |
Issues on the procedure of on-demand SSB SCell operation |
Lenovo |
| R2-2408385 |
Discussion on on-demand SSB for NES |
Ericsson |
| R2-2408409 |
Discussion on on-demand SSB SCell operation |
Fujitsu |
| R2-2408560 |
Further Discussion on-demand SSB for SCell |
Apple |
| R2-2408612 |
Further discussion on On-demand SSB for SCell |
NEC |
| R2-2408712 |
On-demand SSB Scell operation discussion |
Sony |
| R2-2408770 |
RRM relaxation and RRM offloading |
LG Electronics Inc. |
| R2-2408785 |
Discussion on OD-SSB |
Qualcomm Incorporated |
| R2-2408904 |
On demand SSB transmission for SCell |
InterDigital |
| R2-2409053 |
Discussion on on-demand SSB SCell operation |
Sharp |
| R2-2409086 |
On demand SSB handling |
Nokia, Nokia Shanghai Bell |
| 8.5.3 |
On-demand SIB1 |
|
| R2-2407952 |
Discussion on on-demand SIB1 |
Xiaomi |
| R2-2407991 |
Consideration on on-demand SIB1 issues |
CATT |
| R2-2408005 |
Remaining issues of on-demand SIB1 in idle and inactive mode |
ZTE Corporation, Sanechips |
| R2-2408086 |
Discussion on on-demand SIB1 |
CMCC |
| R2-2408101 |
Discussion on on-demand SIB1 for RRC IDLE and INACTIVE UE |
vivo |
| R2-2408173 |
Discussion on on-demand SIB1 for NES |
Spreadtrum Communications |
| R2-2408241 |
Discussion on on-demand SIB1 |
Sharp |
| R2-2408274 |
Discussion on on-demand SIB1 for NES |
HONOR |
| R2-2408294 |
On-demand SIB1 |
Samsung Electronics Co., Ltd |
| R2-2408386 |
Discussion on on-demand SIB1 for NES |
Ericsson |
| R2-2408410 |
Discussion on on-demand SIB1 procedure for NES |
Fujitsu |
| R2-2408445 |
Discussion on on-demand SIB1 operation for NES |
Huawei, HiSilicon |
| R2-2408454 |
Barring and SIB1-less case 2 |
Vodafone, Deutsche Telekom |
| R2-2408461 |
Open issues for the on-demand SIB1 transmission |
Google |
| R2-2408561 |
Discussion on on-demand SIB1 |
Apple |
| R2-2408600 |
Discussion on On-demand SIB1 signalling details |
NEC |
| R2-2408606 |
Discussion on Ondemand-SIB1 |
KDDI Corporation |
| R2-2408641 |
Remaining essential issues |
Lenovo |
| R2-2408677 |
On-demand SIB1 for Idle/Inactive mode UEs |
III |
| R2-2408713 |
On-demand SIB1 for IDLE/INACTIVE UEs |
Sony |
| R2-2408771 |
On-demand transmission of SIB1 |
LG Electronics Inc. |
| R2-2408772 |
Consideration on on-demand SIB1 |
OPPO |
| R2-2408786 |
Discussion on OD-SIB1 |
Qualcomm Incorporated |
| R2-2408865 |
Detection and access of NES cells with OD-SIB1 |
Rakuten Mobile, Inc |
| R2-2408866 |
Discussion on on-demand SIB1 for NES |
Rakuten Mobile, Inc |
| R2-2408902 |
On-demand SIB1 request and reception |
InterDigital |
| R2-2409087 |
On demand SIB1 handling |
Nokia, Nokia Shanghai Bell |
| R2-2409144 |
Discussion on On-demand SIB1 for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2409156 |
On-demand SIB1 for IDLE/INACTIVE UEs |
CEWiT |
| 8.5.4 |
Adaptation of common signal/channel transmissions |
|
| R2-2407974 |
Report for [POST127][109][NES] (OPPO) |
OPPO |
| R2-2407992 |
Adaptation of Common signal channel transmissions |
CATT |
| R2-2408006 |
Further consideration on paging occasion adaptation |
ZTE Corporation, Sanechips |
| R2-2408102 |
Discussion on adaptation of common signal transmissions |
vivo |
| R2-2408136 |
Discussion on adaptation of common signal channel transmission |
OPPO |
| R2-2408149 |
Adaptation of common signal or channel |
Fujitsu |
| R2-2408190 |
Discussion on common signal adaptation |
Xiaomi |
| R2-2408238 |
Discussion on adaptation of common signals/channels transmissions |
Huawei, HiSilicon |
| R2-2408296 |
Adaptation of common signal channel transmissions |
Samsung Electronics Co., Ltd |
| R2-2408322 |
Discussion on the adaptation transmissions for NES operation |
Lenovo |
| R2-2408562 |
Further discussion on common signal transmission adaptation |
Apple |
| R2-2408601 |
PRACH and Paging adaptation |
NEC |
| R2-2408684 |
Discussion on paging adaptation scheme for NES cell |
ITRI |
| R2-2408718 |
Considerations on adaptation for paging signals |
Sony |
| R2-2408794 |
Discussion on adaptation of common signal/channel transmission |
Qualcomm Incorporated |
| R2-2408828 |
Discussion on common signal and channel adaptation |
LG Electronics Inc. |
| R2-2408903 |
Time domain adaptation of common signalling and channels |
InterDigital |
| R2-2408962 |
Adaptation of common signal/channel transmissions for NES |
Ericsson |
| R2-2409061 |
Discussion on RACH adaptation for NES |
SHARP Corporation |
| R2-2409088 |
Common signal aspects of NES WI |
Nokia, Nokia Shanghai Bell |
| R2-2409146 |
Adaptation of Common Signals and Channels for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2409148 |
Adaptation of common signal/channel transmissions |
III |
| R2-2409372 |
[AT127bis][110][NES] (OPPO) |
OPPO |
| 8.6.1 |
Organizational |
|
| R2-2408052 |
Introduction of NR mobility enhancements Phase 4 in TS 37.340 |
China Telecom |
| R2-2408595 |
Important aspects of Rel-19 mobility enhancements WI |
Rapporteurs (Apple, China Telecom) |
| R2-2408598 |
Introduction of NR mobility enhancements Phase 4 in TS 38.300 |
Apple |
| 8.6.2 |
Inter-CU LTM |
|
| R2-2407987 |
Discussion on Inter-CU LTM |
CATT |
| R2-2408053 |
Discussion on inter-CU LTM in DC |
China Telecom |
| R2-2408061 |
Discussion on remaining issues of inter-CU LTM cell switch |
Transsion Holdings |
| R2-2408087 |
Discussion on Inter-CU LTM |
CMCC |
| R2-2408117 |
Discussion on inter-CU LTM |
vivo |
| R2-2408193 |
Discussion on inter-CU LTM |
Xiaomi |
| R2-2408259 |
Discussion on Inter-CU LTM standalone and DC |
MediaTek Inc. |
| R2-2408279 |
Further discussion on inter-CU LTM |
HONOR |
| R2-2408292 |
Discussion on Inter CU LTM |
Lekha Wireless Solutions |
| R2-2408319 |
Discussion on Inter-CU LTM |
Lenovo |
| R2-2408328 |
Discussion on issues for supporting inter-CU LTM |
Sharp |
| R2-2408498 |
Discussion on open issues for inter-CU LTM |
OPPO |
| R2-2408524 |
Discussion on inter-CU LTM |
ZTE Corporation |
| R2-2408596 |
Open items for inter-CU LTM in SA and DC cases |
Apple |
| R2-2408607 |
Discussion on inter-CU LTM with DC |
LG Electronics Inc. |
| R2-2408659 |
Discussion on inter-CU LTM |
NEC |
| R2-2408682 |
The Rel-19 ID for subsequent inter-CU LTM |
ITRI |
| R2-2408714 |
LTM for Inter-CU |
Sony |
| R2-2408752 |
On Inter-CU LTM Open Issues |
Nokia |
| R2-2408758 |
DC aspects for inter-CU LTM |
Ericsson |
| R2-2408860 |
Further Considerations to Support Inter-CU LTM |
Samsung |
| R2-2408867 |
Initial considerations for inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2408870 |
LTM in DC scenarios |
Rakuten Mobile, Inc |
| R2-2408876 |
LTM in DC scenarios |
Rakuten Mobile, Inc |
| R2-2408957 |
Discussion on Inter-CU LTM |
InterDigital, Europe, Ltd. |
| R2-2408959 |
Further Discussion to Support the inter -CU LTM |
ETRI |
| R2-2408966 |
Inter-gNB LTM |
Qualcomm Innovation Center Inc |
| R2-2409000 |
Discussion on Inter-CU LTM |
Kyocera |
| R2-2409009 |
Discussion on fast LTM recovery support for Rel-19 LTM |
Fujitsu |
| R2-2409031 |
Multiple reference configuration for inter-CU LTM |
KDDI Corporation, LG Electronics, Nokia, ZTE, Rakuten, KT, CMCC, ETRI, ITL, ITRI, Fujitsu, SK telecom, Uplus |
| R2-2409142 |
Inter-CU LTM |
Huawei, HiSilicon |
| R2-2409374 |
[AT127bis][112][MOB] Inter-CU SCG LTM& Inter-CU MCG LTM with SCG (ZTE) |
ZTE Corporation |
| R2-2409378 |
LS on RAN2 agreements for inter-CU LTM |
RAN2 |
| 8.6.3 |
L1 event triggered measurement reporting |
|
| R2-2407988 |
L1 event triggered measurement reporting |
CATT |
| R2-2408021 |
Remaining issues of L1 event triggered measurement reporting |
Xiaomi |
| R2-2408054 |
Discussion on L1 event triggered measurement reporting |
China Telecom |
| R2-2408062 |
Discussion on L1 event triggered measurement reporting |
Transsion Holdings |
| R2-2408070 |
Discussion on L1 event triggered measurement reporting |
CMCC |
| R2-2408118 |
Discussion on LTM measurement event evaluation and reporting |
vivo |
| R2-2408150 |
Discussions on event triggered L1 measurement reporting |
Fujitsu |
| R2-2408164 |
Discussion on L1 event triggered measurement reporting |
Spreadtrum Communications |
| R2-2408260 |
Measurement reporting discussion |
MediaTek Inc. |
| R2-2408280 |
Discussion on measurement event evaluation and report |
HONOR |
| R2-2408320 |
L1 Measurement enhancements |
Lenovo |
| R2-2408329 |
Discussion on issues for L1 event triggered measurement reporting |
Sharp |
| R2-2408384 |
Discussion on LTM measurement reporting configuration |
Baicells |
| R2-2408455 |
L1 measurement event configuration and reporting |
Panasonic |
| R2-2408492 |
Discussion on L1 event triggered measurement |
Jio |
| R2-2408499 |
Open issues for event triggered L1 measurement reporting |
OPPO |
| R2-2408525 |
Discussion on L1 event triggered measurement reporting |
ZTE Corporation |
| R2-2408597 |
LTM event triggered measurement reporting |
Apple |
| R2-2408613 |
Details of L1 event triggered measurement reporting |
NEC |
| R2-2408759 |
Event definition and MAC CE content for L1 event-triggered measurements |
Ericsson |
| R2-2408783 |
Discussion on event-triggered measurement report |
Huawei, HiSilicon |
| R2-2408871 |
Event based L1 measurements triggered LTM candidate cell addition/release |
Rakuten Mobile, Inc |
| R2-2408948 |
On L1 Measurement Reporting Enhancements for Rel-19 LTM |
Nokia |
| R2-2408965 |
Measurement enhancements for LTM |
Qualcomm Incorporated |
| R2-2408996 |
L1 measurement reporting procedures for LTM enhancements |
Kyocera |
| R2-2409033 |
Discussion on Event-triggered L1 measurement reporting |
NTT DOCOMO, INC. |
| R2-2409065 |
Event LTM report |
LG Electronics Inc. |
| R2-2409096 |
Support of Event Triggered L1 Measurement Reporting |
Samsung |
| R2-2409105 |
Discussion on event triggered L1 measurement reporting |
ITL |
| R2-2409127 |
Discussion on L1 event triggered measurement reporting |
KDDI Corporation |
| R2-2409192 |
Event triggered L1 measurement reporting for LTM |
Interdigital, Inc. |
| R2-2409206 |
Remaining issues of L1 event triggered measurement reporting |
Xiaomi |
| 8.6.4 |
Conditional intra-CU LTM |
|
| R2-2407989 |
Discussion on Conditional Intra-CU LTM |
CATT |
| R2-2408055 |
Discussion on conditional intra-CU LTM |
China Telecom |
| R2-2408063 |
Discussion on supporting conditional intra-CU LTM |
Transsion Holdings |
| R2-2408088 |
Disucssion on conditional LTM |
CMCC |
| R2-2408119 |
Discussion on conditional LTM |
vivo |
| R2-2408151 |
Discussion on conditional LTM |
Fujitsu |
| R2-2408165 |
Discussion on conditional intra-CU LTM |
Spreadtrum Communications |
| R2-2408194 |
Discussion on conditional LTM |
Xiaomi |
| R2-2408261 |
Initial thinking on conditional LTM |
MediaTek Inc. |
| R2-2408281 |
Discussion on conditional LTM |
HONOR |
| R2-2408330 |
Discussion on conditional LTM |
Sharp |
| R2-2408500 |
Discussion on conditional LTM |
OPPO |
| R2-2408507 |
Considerations for conditional LTM |
Panasonic |
| R2-2408526 |
Discussion on conditional intra-CU LTM |
ZTE Corporation |
| R2-2408599 |
Scoping conditional LTM for Rel-19 |
Apple |
| R2-2408608 |
Discussion on conditional LTM |
LG Electronics Inc. |
| R2-2408614 |
Discussion on conditional intra-CU LTM |
NEC |
| R2-2408640 |
Conditional LTM basics |
Lenovo |
| R2-2408724 |
Conditional Intra-CU LTM |
Sony |
| R2-2408760 |
Baseline assumptions for conditional LTM |
Ericsson |
| R2-2408928 |
On conditional LTM |
Nokia |
| R2-2408960 |
Discussion on conditional intra-CU LTM |
ETRI |
| R2-2408964 |
Conditional intra-gNB LTM |
Qualcomm Incorporated |
| R2-2408997 |
Discussion on Conditional LTM |
KT Corp. |
| R2-2409001 |
Discussion on Conditional Intra-CU LTM |
Kyocera |
| R2-2409035 |
Discussion on Conditional intra-CU LTM |
NTT DOCOMO, INC. |
| R2-2409097 |
Support of Conditional Intra-CU LTM |
Samsung |
| R2-2409106 |
Discussion on Conditional LTM |
ITL |
| R2-2409111 |
Discussion on Conditional mobility |
CEWiT |
| R2-2409143 |
Intra-CU conditional LTM |
Huawei, HiSilicon |
| R2-2409193 |
Conditional LTM |
Interdigital, Inc. |
| 8.7.1 |
Organizational |
|
| R2-2407927 |
Response LS to SA2 on FS_XRM Ph2 (R3-244844; contact: ZTE) |
RAN3 |
| R2-2407936 |
LS reply on multi-modality awareness at RAN (S2-2409444; contact: Huawei) |
SA2 |
| R2-2407939 |
LS Reply on FS_XRM_Ph2 (S4-241776; contact: Nokia) |
SA4 |
| R2-2407940 |
LS on Application-Layer FEC Awareness at RAN (S4-241785; contact: Qualcomm) |
SA4 |
| R2-2408645 |
Rapporteur Inputs |
Nokia, Qualcomm (Rapporteurs) |
| R2-2408693 |
Discussion on multi-modality LS |
InterDigital |
| R2-2408782 |
Discussion on reply LS on multi-modality awareness |
Huawei, HiSilicon |
| R2-2409271 |
[DRAFT] Reply on FS_XRM_Ph2 |
Nokia |
| R2-2409272 |
Reply to SA2 LS on multi-modality awareness |
RAN2 |
| R2-2409390 |
Reply on FS_XRM_Ph2 |
RAN2 |
| 8.7.2 |
Multi-modality support |
|
| R2-2408120 |
Discussion on LS from SA2 on multi-modality |
vivo |
| R2-2408535 |
Reply LS on multi-modality support |
ZTE Corporation, Sanechips |
| R2-2408627 |
Discussion on LS from SA2 on multi-modality awareness at RAN |
Meta |
| R2-2409082 |
Draft Reply LS on multi-modality awareness at RAN |
Nokia, Nokia Shanghai Bell |
| 8.7.3 |
RRM measurement gaps/restrictions related enhancements |
|
| R2-2407998 |
Enabling TX RX for XR during RRM measurements |
CATT |
| R2-2408074 |
Discussion on RRM measurement gaps enhancements |
CMCC |
| R2-2408129 |
Discussion on overriding measurement gaps |
Qualcomm Incorporated |
| R2-2408347 |
Enabling TX/RX for XR during RRM measurement gaps /restrictions |
Lenovo |
| R2-2408425 |
Discussion on RRM measurement gaps enhancements of XR traffic |
Xiaomi Communications |
| R2-2408575 |
Views on Enhancements Relating to RRM Measurement Gaps |
Apple |
| R2-2408610 |
Discussion on RRM measurement gaps/restrictions related enhancements |
NEC |
| R2-2408617 |
Measurement Gap Enhancements for XR |
Sharp |
| R2-2408628 |
Discussion on RRM Measurement Gaps/Restrictions Enhancements |
Meta |
| R2-2408689 |
RRM Measurement Gaps/Restrictions related enhancements for XR |
Google Ireland Limited |
| R2-2408720 |
Discussion on enabling TX/RX for XR during RRM measurements |
Sony |
| R2-2408781 |
Discussion on RRM enhancements for XR |
Huawei, HiSilicon |
| R2-2408882 |
XR - RRM Measurement Gap/Restriction Enhancements |
Ericsson |
| R2-2408986 |
Discussion on RRM measurement gaps/restrictions enhancements for Rel-19 XR |
Samsung |
| R2-2409016 |
RRM measurement gaps/restrictions related enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2409116 |
Discussion on Measurement Gap enhancements |
OPPO |
| R2-2409147 |
Discussion on XR RRM measurement gaps/restrictions related enhancements |
III |
| R2-2409151 |
Discussion on MG enhancement for XR |
LG Electronics Inc. |
| 8.7.4 |
Scheduling enhancements |
|
| R2-2408346 |
Enhanced Logical channel prioritization (LCP) for XR |
Lenovo |
| R2-2409145 |
Discussion on XR scheduling enhancements |
III |
| 8.7.4.1 |
LCP enhancements |
|
| R2-2407999 |
Consideration on LCP enhancement |
CATT |
| R2-2408094 |
Consideration on LCP enhancement for XR |
CMCC |
| R2-2408106 |
Discussion on additional Logical Channel priority handling |
TCL |
| R2-2408121 |
Discussion on LCP enhancement for XR |
vivo |
| R2-2408130 |
Discussion on LCP enhancements |
Qualcomm Incorporated |
| R2-2408134 |
Discussion on delay-aware LCP enhancements for XR |
OPPO |
| R2-2408152 |
Discussions on enhancement of the LCP for delay-critical data |
Fujitsu |
| R2-2408177 |
Discussion on LCP enhancements for XR |
Spreadtrum Communications |
| R2-2408286 |
Discussion on LCP enhancements |
HONOR |
| R2-2408343 |
Considerations on LCP enhancements for XR |
NEC |
| R2-2408421 |
Additional LCH Priority Handling and Prioritization |
Sharp |
| R2-2408426 |
Discussion on LCP enhancements of XR traffic |
Xiaomi Communications |
| R2-2408495 |
Discussion on Logical channel priority |
CANON Research Centre France |
| R2-2408530 |
LCP enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2408576 |
Delay-based Logical Channel Priority Adjustment |
Apple |
| R2-2408650 |
Discussion on LCP enhancements for XR |
DENSO CORPORATION |
| R2-2408694 |
LCP enhancements for UL scheduling |
InterDigital |
| R2-2408727 |
Discussion on additional priority based LCP enhancements in XR |
Huawei, HiSilicon |
| R2-2408857 |
Discussion on Leftover Issues for LCP Prioritization |
China Telecom |
| R2-2408907 |
Discussion on additional LCP handling |
ETRI |
| R2-2408916 |
LCP enhancements |
Ericsson |
| R2-2409017 |
LCP Enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2409049 |
LCP enhancements for LCH with delay critical data |
MediaTek Inc. |
| R2-2409149 |
Discussion on LCP enhancement for XR |
LG Electronics Inc. |
| R2-2409155 |
LCP enhancements for Rel-19 XR |
Samsung R&D Institute UK |
| 8.7.4.2 |
DSR enhancements |
|
| R2-2408000 |
Consideration on DSR enhancement |
CATT |
| R2-2408095 |
Consideration on DSR enhancement for XR |
CMCC |
| R2-2408122 |
Discussion on DSR enhancement for XR |
vivo |
| R2-2408131 |
Discussion on DSR enhancements |
Qualcomm Incorporated |
| R2-2408135 |
Discussion on delay-aware DSR enhancements for XR |
OPPO |
| R2-2408153 |
Discussions on DSR enhancements |
Fujitsu |
| R2-2408288 |
Discussion on DSR enhancements |
HONOR |
| R2-2408307 |
Enhanced delay status reporting for XR |
Lenovo |
| R2-2408344 |
Considerations on DSR enhancements for XR |
NEC |
| R2-2408422 |
Considerations for DSR Enhancements |
Sharp |
| R2-2408427 |
Discussion on DSR enhancements of XR traffic |
Xiaomi Communications |
| R2-2408496 |
Discussion on Delay status report |
CANON Research Centre France |
| R2-2408531 |
DSR enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2408577 |
Views on DSR Enhancements |
Apple |
| R2-2408629 |
Discussion on DSR Enhancements |
Meta |
| R2-2408683 |
Discussion on enhanced DSR for XR |
ITRI |
| R2-2408695 |
DSR enhancements for UL scheduling |
InterDigital |
| R2-2408728 |
Discussion on DSR enhancements in XR |
Huawei, HiSilicon |
| R2-2408858 |
Discussion on Remaining Issues for DSR Enhancement |
China Telecom |
| R2-2408918 |
DSR enhancements |
Ericsson |
| R2-2408985 |
DSR enhancements for Rel-19 XR |
Samsung |
| R2-2409018 |
DSR Enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2409074 |
Discussion on DSR enhancement |
TCL |
| R2-2409101 |
Discussion on DSR enhancements |
ETRI |
| R2-2409112 |
Remaining issues for DSR enhancement |
MediaTek Inc. |
| R2-2409150 |
Discussion on DSR enhancement for XR |
LG Electronics Inc. |
| 8.7.5 |
RLC enhancements |
|
| R2-2407986 |
Discussion on RLC AM enhancements |
Huawei, HiSilicon |
| R2-2408001 |
Consideration on XR-specific RLC enhancement |
CATT |
| R2-2408033 |
RLC AM retransmission enhancements |
Xiaomi |
| R2-2408075 |
Discussion on the RLC re-transmission related enhancements for XR |
CMCC |
| R2-2408123 |
Discussion on RLC enhancement for XR |
vivo |
| R2-2408132 |
Discussion on RLC enhancements |
Qualcomm Incorporated |
| R2-2408154 |
Discussions on RLC enhancements |
Fujitsu |
| R2-2408178 |
Discussion on timely RLC retransmission(s) |
Spreadtrum Communications |
| R2-2408287 |
Discussion on timely RLC enhancements |
HONOR |
| R2-2408308 |
AM RLC enhancement |
Lenovo |
| R2-2408424 |
Discussion on Timely Retransmission |
Sharp |
| R2-2408497 |
Discussion on RLC AM Enhancements |
CANON Research Centre France |
| R2-2408532 |
RLC enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2408578 |
Views on RLC-AM Enhancements for Rel-19 XR |
Apple |
| R2-2408630 |
Discussion on RLC AM Enhancements for XR |
Meta |
| R2-2408633 |
RLC Enhancements for XR |
Samsung |
| R2-2408646 |
RLC enhancements |
Nokia |
| R2-2408673 |
Further Discussion on RLC AM enhancement |
NEC |
| R2-2408696 |
Discussion on RLC retransmission enhancements |
InterDigital |
| R2-2408697 |
Avoiding unnecessary RLC re-transmissions |
InterDigital |
| R2-2408715 |
RLC AM enhancements |
Sony |
| R2-2408859 |
Discussion on RLC Enhancement |
China Telecom |
| R2-2408883 |
Even Further Discussions on RLC AM Enhancements |
Ericsson |
| R2-2408982 |
Discussion on further details of RLC enhancements for XR |
LG Electronics Inc. |
| R2-2409073 |
Discussion on RLC AM enhancement |
TCL |
| R2-2409115 |
Discussion on RLC re-transmission related enhancements |
OPPO, China Telecom, Sharp, Samsung, HONOR, CMCC, KDDI, Apple, Intel,
vivo, MediaTek, ZTE |
| R2-2409153 |
RLC AM enhancements with small packet delay budget |
MediaTek Inc. |
| R2-2409208 |
Discussion on RLC re-transmission related enhancements |
OPPO, China Telecom, Sharp, Samsung, HONOR, CMCC, KDDI, Apple, Intel, vivo, MediaTek, ZTE, CANON |
| 8.7.6 |
XR rate control |
|
| R2-2408002 |
Discussion on XR rate control |
CATT |
| R2-2408034 |
XR rate control |
Xiaomi |
| R2-2408096 |
Consideration on rate control enhancement for XR |
CMCC |
| R2-2408107 |
Discussion on XR rate control |
TCL |
| R2-2408124 |
Discussion on codec rate adaption |
vivo |
| R2-2408133 |
Discussion on signaling enhancements for XR rate control |
Qualcomm Incorporated |
| R2-2408345 |
Uplink rate control for XR |
NEC |
| R2-2408423 |
UL Congestion Signaling Enhancements for XR |
Sharp |
| R2-2408491 |
XR Rate Control |
Lenovo |
| R2-2408533 |
MAC signalling for data rate control for XR applications |
ZTE Corporation, Sanechips |
| R2-2408579 |
Views on MAC Signalling for XR Rate Control |
Apple |
| R2-2408631 |
Discussion on RAN Awareness and UL Rate Control for XR |
Meta |
| R2-2408722 |
Recommended bit rate based XR rate control |
Sony |
| R2-2408773 |
Discussion on uplink congestion signalling |
OPPO |
| R2-2408780 |
Discussion on XR rate control |
Huawei, HiSilicon |
| R2-2408884 |
On XR Rate Control |
Ericsson |
| R2-2408983 |
Discussion on rate control signaling for XR |
LG Electronics Inc. |
| R2-2408984 |
Discussion on UL rate control for Rel-19 XR |
Samsung |
| R2-2409077 |
XR rate control |
Nokia, Nokia Shanghai Bell |
| R2-2409084 |
Uplink congestion control signalling |
MediaTek Inc. |
| R2-2409174 |
Discussions on XR UL rate control |
Futurewei |
| R2-2409273 |
LS on appropriate range and granularity of bit rate adaptation for XR applications |
RAN2 |
| 8.8.1 |
Organizational |
|
| R2-2407919 |
Reply LS on DL coverage enhancements (R1-2407538; contact: CMCC) |
RAN1 |
| R2-2407963 |
Introduction of LTE TN to NR NTN IDLE mode mobility |
CATT |
| R2-2408014 |
Introduction of LTE TN to NR NTN Mobility UE Capability |
vivo |
| R2-2408805 |
Stage 2 Running CR for E-UTRAN to NR NTN mobility |
Samsung |
| R2-2409183 |
Running RRC CR for NR NTN phase 3 |
Ericsson |
| 8.8.2 |
Downlink coverage enhancements |
|
| R2-2407960 |
Discussion on Downlink Coverage Enhancements |
CATT |
| R2-2407983 |
Consideration on downlink coverage enhancements |
NERCDTV |
| R2-2408015 |
Discussion on Cell Bar Control for DL Coverage Enhancement |
vivo |
| R2-2408046 |
Discussion of NR NTN coverage enhancement |
China Telecom |
| R2-2408097 |
RAN2 Impact on DL coverage enhancements |
CMCC |
| R2-2408155 |
Discussions on cell DTX during satellite dynamic power sharing |
Fujitsu |
| R2-2408160 |
Discussion on DL coverage enhancement for NTN |
OPPO |
| R2-2408284 |
Discussion on downlink coverage enhancement |
HONOR |
| R2-2408300 |
Access control for NTN downlink coverage enhancement |
Lenovo |
| R2-2408337 |
Discussion on DL coverage enhancements |
Huawei, HiSilicon, Turkcell |
| R2-2408411 |
Consideration on downlink coverage enhancement |
NEC Corporation. |
| R2-2408459 |
DL coverage enhancement at system level |
Google |
| R2-2408465 |
Discussion on cell DTX/DRX for NTN |
Xiaomi |
| R2-2408593 |
DL coverage enhancement in NTN |
Apple |
| R2-2408655 |
Consideration on downlink coverage enhancements |
ZTE Corporation, Sanechips |
| R2-2408699 |
Discussion on NTN downlink coverage enhancement |
Nokia |
| R2-2408719 |
SMTC impacts due to NTN downlink coverage enhancements |
Sony |
| R2-2408739 |
Discussion on Downlink Coverage Enhancements |
CSCN |
| R2-2408894 |
Discussion on cell DTX |
Qualcomm Incorporated |
| R2-2408920 |
Downlink coverage enhancement for NTN |
InterDigital |
| R2-2408970 |
Downlink coverage enhancement SMTC impacts |
Sequans Communications |
| R2-2408981 |
Discussion on downlink coverage enhancements |
LG Electronics Inc. |
| R2-2409004 |
Discussion on Downlink Coverage Enhancements |
Sharp |
| R2-2409025 |
Discussion on Downlink Coverage Enhancement |
Samsung |
| R2-2409051 |
Discussion on the impact of SSB extension for NR NTN |
NTPU |
| R2-2409180 |
DL coverage enhancements |
Ericsson |
| 8.8.4 |
Support of Broadcast service |
|
| R2-2407961 |
Discussion on support of broadcast service in NR NTN |
CATT |
| R2-2407982 |
Discussion on support of broadcast service in NTN |
NERCDTV |
| R2-2408016 |
Further Discussion on MBS Broadcast Provision in NTN |
vivo |
| R2-2408047 |
Consideration of service area in NR NTN |
China Telecom |
| R2-2408080 |
Discussion on MBS broadcast service for NR NTN |
CMCC |
| R2-2408138 |
Discussion on providing MBS service area in NTN network |
OPPO |
| R2-2408156 |
Discussions on supporting broadcast intended to serve partial cell |
Fujitsu |
| R2-2408285 |
Discussion on the support of broadcast service |
HONOR |
| R2-2408301 |
Further considerations for broadcast service area indication |
Lenovo |
| R2-2408338 |
Discussion on MBS broadcast over NTN |
Huawei, HiSilicon, Turkcell |
| R2-2408464 |
Discussion on Support of MBS Broadcast Service over NTN |
TCL |
| R2-2408488 |
Discussion on MBS Broadcast service area signaling |
THALES |
| R2-2408592 |
Intended broadcast service area provision over NTN |
Apple |
| R2-2408602 |
Further details on intended service area for MBS and ETWS |
NEC |
| R2-2408619 |
Discussion on the support of broadcast service |
Xiaomi |
| R2-2408656 |
Consideration on broadcast service ehancements |
ZTE Corporation, Sanechips |
| R2-2408685 |
Discussions on MCCH reacquiring |
ITRI |
| R2-2408892 |
Signaling of MBS broadcast service area information |
Qualcomm Incorporated |
| R2-2408946 |
On MBS Support in Rel-19 NR NTN |
Nokia, Nokia Shanghai Bell |
| R2-2408958 |
Support for broadcast service in non-terrestrial networks |
InterDigital, Europe, Ltd. |
| R2-2408988 |
Discussion on support of broadcast service in NTN |
LG Electronics France |
| R2-2409002 |
UE behaviour for MBS related procedures |
Sharp |
| R2-2409003 |
Discussion on MBS service area information |
Sharp |
| R2-2409026 |
Discussion on MBS Broadcast Service Intended Area |
Samsung |
| R2-2409113 |
Remaining issues for the support of broadcast service in NTN |
ETRI |
| R2-2409184 |
Support for broadcast services in NR NTN |
Ericsson |
| 8.8.5 |
Support of regenerative payload |
|
| R2-2407962 |
Further discussion on regenerative payload |
CATT |
| R2-2408161 |
Discussion on satellite switch with resynch for regenerative payload |
OPPO |
| R2-2408283 |
Discussion on regenerative payload |
HONOR |
| R2-2408302 |
UE location verification in NTN regenerative architecture |
Lenovo |
| R2-2408339 |
Discussion on regenerative payload |
Huawei, HiSilicon, Turkcell |
| R2-2408657 |
Consideration on NTN remaining issues |
ZTE Corporation, Sanechips |
| R2-2408716 |
Satellite switch with re-sync in regenerative payload |
Sony |
| R2-2408806 |
On adaptations related to regenerative payload for NR NTN |
Samsung |
| R2-2408893 |
Discussion on regenerative payload |
Qualcomm Incorporated |
| R2-2408947 |
Remaining Issues for NTN over Regenerative Architecture |
Nokia, Nokia Shanghai Bell |
| R2-2408980 |
Discussion on regenerative payload |
Fujitsu Limited |
| R2-2409071 |
Discussion on support of regenerative payload |
ETRI |
| R2-2409179 |
Regenerative payload |
Ericsson |
| 8.8.6 |
LTE to NR NTN mobility |
|
| R2-2407964 |
Open issue list and rapporteur's input for LTE_TN_NR_NTN_mob |
CATT |
| R2-2408048 |
Signaling design optimization for satellite information |
China Telecom |
| R2-2408081 |
Discussion on left issues of LTE to NR mobility |
CMCC |
| R2-2408257 |
SIB33 multi-beam signalling |
PANASONIC |
| R2-2408674 |
Remaining Issues on NR Satellite Info Provision in LTE TN cell |
NEC |
| 8.9.1 |
Organizational |
|
| R2-2407920 |
Reply LS to RAN2 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 (R1-2407548; contact: ZTE) |
RAN1 |
| R2-2407931 |
Reply LS to RAN2 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 (R4-2414114; contact: ZTE) |
RAN4 |
| R2-2407938 |
LS on reply to LS on FS_5GSAT_Ph3_ARCH conclusions (S3-243533; contact: Nokia) |
SA3 |
| R2-2408635 |
Revised work Plan for Rel-19 IoT NTN |
MediaTek Inc. |
| R2-2409182 |
Introduction of IoT NTN phase 3 |
Ericsson |
| 8.9.2 |
Support of Store & Forward |
|
| R2-2407966 |
Discussion on RAN2 impacts due to the satellite ID list from MME in S&F operation |
CATT |
| R2-2408017 |
RAN2 Aspect for S&F Operation |
vivo |
| R2-2408049 |
Remaining issues of IoT NTN Store & Forward |
China Telecom |
| R2-2408064 |
Discussion on support of Store&Forward |
Transsion Holdings |
| R2-2408066 |
Discussion on IoT NTN Store and Forward |
CMCC |
| R2-2408108 |
Further consideration on Store and Forward |
Huawei, HiSilicon, Turkcell, China Southern Power Grid |
| R2-2408244 |
Considerations on S&F operation from device perspective |
Telit Communications S.p.A., Novamint, Sateliot, Thales |
| R2-2408282 |
Discussion on the Store and Forward satellite operation |
HONOR |
| R2-2408303 |
Access control and information exchange for Store and Forward operation |
Lenovo |
| R2-2408333 |
Further consideration on S&F operation in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2408360 |
Discussion on information for Store & Forward |
ASUSTeK |
| R2-2408389 |
Access Control for Store and Forward Operation |
CATT, Huawei, HiSilicon, CMCC, vivo |
| R2-2408460 |
Access control and the S&F indication |
Google |
| R2-2408501 |
Discussion on Store & Forward satellite operation |
OPPO |
| R2-2408591 |
Support of S&F operation in IoT NTN |
Apple |
| R2-2408620 |
Discussion on the support of store and forward |
Xiaomi |
| R2-2408622 |
RAN2 impact on S&F mode |
MediaTek Inc. |
| R2-2408675 |
Radio Interface Aspect of Store and Forward |
NEC |
| R2-2408754 |
On RAN2 Impacts of SF Operation |
Nokia, Nokia Shanghai Bell |
| R2-2408802 |
Discussion on Store and Forward |
Samsung |
| R2-2408895 |
Discussion on S&F mode operation |
Qualcomm Incorporated |
| R2-2408905 |
Considerations on multi-satellite for S&F Satellite operation |
NOVAMINT, Sateliot |
| R2-2408956 |
Considerations on Store & Forward Satellite Operation |
SHARP Corporation |
| R2-2408971 |
Support of Store & Forward |
Sequans Communications |
| R2-2409064 |
Discussion on Store & Forward operation |
DENSO CORPORATION |
| R2-2409189 |
Support of Store and Forward |
InterDigital, Inc. |
| 8.9.3 |
Uplink Capacity Enhancement |
|
| R2-2407965 |
Further consideration on UL capacity enhancements |
CATT |
| R2-2408018 |
Discussion on CB-Msg3 EDT Enhancement |
vivo |
| R2-2408050 |
Support Contention-based Msg3-EDT in IoT NTN |
China Telecom |
| R2-2408065 |
Discussion on uplink capacity enhancement |
Transsion Holdings |
| R2-2408082 |
Further discussion on uplink capacity enhancement for IoT-NTN |
CMCC |
| R2-2408109 |
Discussion on the mechanisms for UL capacity enhancement based on simulation results |
Huawei, HiSilicon, CTCC, CATT, Nokia, Nokia Shanghai Bell, Apple, Turkcell, China Southern Power Grid |
| R2-2408163 |
Uplink Capacity Enhancement for EDT transaction |
Spreadtrum Communications |
| R2-2408304 |
EDT for uplink capacity enhancement in NTN |
Lenovo |
| R2-2408334 |
Comparison of solutions for UL capacity enhancements in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2408413 |
Consideration on UL capacity enhancement for IoT-NTN |
NEC Corporation. |
| R2-2408466 |
Discussion on uplink capacity enhancements for IOT NTN |
Xiaomi |
| R2-2408502 |
Discussion on enhanced EDT for IoT NTN |
OPPO |
| R2-2408545 |
Repetitions and Delay Considerations about SA and DSA |
ESA, Eutelsat Group, Viasat, Inmarsat, Novamint, Echostar, Sateliot, Toyota ITC |
| R2-2408547 |
Repetitions and Delay Considerations about SA and DSA |
ESA, Eutelsat Group, Viasat, Inmarsat, Novamint, Echostar, Sateliot, Toyota ITC |
| R2-2408590 |
Uplink capacity enhancement in IoT NTN |
Apple |
| R2-2408623 |
Discussion on enhanced EDT |
MediaTek Inc. |
| R2-2408803 |
Procedures for uplink capacity enhancements for IoT NTN |
Samsung |
| R2-2408831 |
Discussion on UL capacity enhancement for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2408863 |
Discussion on throughput and delay performance of slotted ALOHA and diversity slotted ALOHA |
DLR, ESA |
| R2-2408896 |
Discussion on EDT enhancements |
Qualcomm Incorporated |
| R2-2409170 |
Operator views on EDT enhancements and CRDSA |
Inmarsat, Viasat |
| R2-2409181 |
UL capacity enhancements for IoT NTN |
Ericsson |
| R2-2409190 |
EDT/PUR enhancements |
InterDigital, Inc. |
| R2-2409231 |
Report of [AT127bis][301][R19 IoT NTN] Working point for CB-msg3 |
NEC |
| R2-2409239 |
Draft LS on OCC for CB-msg3 NPUSCH |
vivo |
| R2-2409242 |
LS on OCC for CB-msg3 NPUSCH |
RAN2 |
| 8.9.4 |
Support of PWS |
|
| R2-2408019 |
Discussion on the Support of PWS in IoT-NTN |
vivo, Apple |
| R2-2408051 |
Support PWS in IoT NTN |
China Telecom |
| R2-2408083 |
Discussion on broadcast of PWS messages for NB-IoT |
CMCC |
| R2-2408110 |
Support of PWS for NB-IoT |
Huawei, HiSilicon, Turkcell, China Southern Power Grid |
| R2-2408305 |
PWS broadcast support for NB-IoT in NTN |
Lenovo |
| R2-2408335 |
PWS support for NB-IoT over NTN |
ZTE Corporation, Sanechips |
| R2-2408412 |
Consideration on PWS broadcast for NB-IoT |
NEC Corporation. |
| R2-2408621 |
Discussion one the support of broadcast of PWS for NB-IoT |
Xiaomi |
| R2-2408624 |
Discussion on supporting PWS for NB-IoT |
MediaTek Inc. |
| R2-2408804 |
Impact of PWS signalling for NB-IoT |
Samsung |
| R2-2408826 |
Discussion on Emergency Broadcast for NB-IoT |
Inmarsat, Viasat |
| R2-2408832 |
Support of PWS for NB-IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2408897 |
Discussion on PWS in NB-IoT NTN |
Qualcomm Incorporated |
| R2-2408998 |
Discussion on broadcast of PWS message for NB-IoT |
KT Corp. |
| R2-2409191 |
Support of PWS |
Interdigital, Inc. |
| R2-2409237 |
Draft LS on PWS support for NB-IoT NTN in NTN |
Interdigital |
| R2-2409243 |
LS on PWS support for NB-IoT NTN |
RAN2 |
| 8.10.1 |
Organizational |
|
| R2-2407925 |
LS on SON for Network Slicing and enhanced area scope (R3-244823; contact: Nokia) |
RAN3 |
| R2-2409218 |
Way forward for Rel-19 SON_MDT in RAN2 |
China Unicom |
| R2-2409297 |
LS to RAN3 on way forward on Rel-19 SONMDT |
RAN2 |
| 8.10.2 |
MRO enhancements for Rel-18 mobility features |
|
| R2-2408056 |
MRO for Rel-18 mobility features |
vivo |
| R2-2408090 |
MRO enhancements for CHO with candidate SCGs |
CMCC |
| R2-2408091 |
MRO enhancements for LTM |
CMCC |
| R2-2408185 |
Discussion on MRO enhancement for R18 mobility features |
SHARP Corporation |
| R2-2408199 |
Discussion on MRO Enhancements for Rel-18 Mobility |
CATT |
| R2-2408316 |
Discussion on MRO for R18 mobility |
Lenovo |
| R2-2408354 |
Discussion on random access report for LTM |
ASUSTeK |
| R2-2408379 |
MRO for CHO with candidate SCG |
Nokia |
| R2-2408380 |
MRO for LTM |
Nokia |
| R2-2408381 |
Discussion on MRO enhancement for LTM |
China Unicom |
| R2-2408382 |
Discussion on MRO enhancement for CHO with candidate SCGs |
China Unicom |
| R2-2408405 |
More on failure and near failure cases for LTM |
ZTE Corporation, Sanechips |
| R2-2408406 |
More on CHO with candidate SCGs |
ZTE Corporation, Sanechips |
| R2-2408435 |
MRO enhancements for Rel-18 mobility features |
Samsung |
| R2-2408749 |
MRO enhancements for LTM |
NEC |
| R2-2408750 |
MRO for CHO with candidate SCG(s) |
NEC |
| R2-2408766 |
MRO enhancement for SON and MDT |
Qualcomm Incorporated |
| R2-2408824 |
SON support for MRO |
Ericsson |
| R2-2408835 |
Discussion on MRO enhancements for Rel-18 mobility features |
Huawei, HiSilicon |
| R2-2408873 |
Configuring UE based TA acquisition for LTM |
Rakuten Mobile, Inc |
| R2-2408979 |
SON/MDT reports for LTM |
Kyocera |
| R2-2409041 |
MRO for MOB DCCA |
LG Electronics |
| R2-2409042 |
MRO for MOB LTM |
LG Electronics |
| 8.10.5 |
Leftovers from Rel-18 |
|
| R2-2408057 |
RACH optimization for SDT |
vivo |
| R2-2408187 |
Discussion on RACH enhancement for SDT |
SHARP Corporation |
| R2-2408198 |
Consideration on leftovers from Rel-18 SONMDT |
CATT |
| R2-2408317 |
Discussion on RACH optimization for SDT |
Lenovo |
| R2-2408437 |
Reporting failure cause for SDT |
Samsung |
| R2-2408494 |
SON/MDT enhancements for leftover topics from R18 |
Jio |
| R2-2408767 |
SON and MDT for SDT |
Qualcomm Incorporated |
| R2-2408836 |
Discussion on support of the Rel-18 leftovers |
Huawei, HiSilicon |
| R2-2409163 |
On Rel.18 leftovers |
Ericsson |
| 8.11.1 |
Organizational |
|
| R2-2407917 |
LS to RAN3 on PHY/L1 aspects of information exchange among gNBs for CLI mitigation (R1-2407533; contact: Ericsson) |
RAN1 |
| 8.11.2 |
Random access in SBFD |
|
| R2-2407950 |
Random Access in SBFD symbols |
CATT |
| R2-2407955 |
Discussion on RACH in SBFD |
Xiaomi |
| R2-2408067 |
Discussion on random access in SBFD |
CMCC |
| R2-2408103 |
Discussion on random access procedure in SBFD |
vivo |
| R2-2408219 |
Discussion on random access procedure in SBFD |
ZTE Corporation |
| R2-2408364 |
Impacts on the random access by the evolution of duplex operation |
Huawei, HiSilicon |
| R2-2408420 |
Random Access Procedures for SBFD |
Sharp |
| R2-2408508 |
SBFD RACH configuration for initial random access |
Charter Communications, Inc |
| R2-2408550 |
Random Access for SBFD Operation |
NEC |
| R2-2408594 |
Framework to support RACH in SBFD |
Apple |
| R2-2408647 |
Random Access Operation of SBFD |
Nokia Corporation |
| R2-2408690 |
Random access in Sub-Band Full Duplex |
Google Ireland Limited |
| R2-2408717 |
Random access for SBFD Operation |
Sony |
| R2-2408799 |
Views on random access for SBFD |
Qualcomm Incorporated |
| R2-2408855 |
SBFD RA aspects |
Ericsson |
| R2-2409008 |
Random access in SBFD |
Samsung |
| R2-2409152 |
Discussion on Random Access procedure for SBFD |
LG Electronics Inc. |
| 8.11.3 |
Other aspects |
|
| R2-2407951 |
Discussion on other aspects for SBFD |
CATT |
| R2-2408035 |
Other aspects of SBFD |
Xiaomi |
| R2-2408089 |
Discussion on SBFD related issues |
CMCC |
| R2-2408104 |
Discussion on other aspects in SBFD |
vivo |
| R2-2408220 |
Discussion on CLI measurement in SBFD |
ZTE Corporation |
| R2-2408365 |
Discussion on the SBFD configuration and CLI measurement |
Huawei, HiSilicon |
| R2-2408800 |
Other aspects of SBFD |
Qualcomm Incorporated |
| R2-2408856 |
Non-RA aspects for subband full duplex (SBFD) operation |
Ericsson |
| R2-2409089 |
Other aspects of SBFD |
Nokia |
| R2-2409098 |
Support of Cross Link Interference in SBFD |
Samsung |
| 8.12.1 |
Organizational |
|
| R2-2407906 |
LS to RAN2 on RRC and MAC CE impacts for Rel-19 NR MIMO Ph5 (R1-2407285; contact: Samsung) |
RAN1 |
| R2-2408909 |
Running CR for MIMO Phase 5 |
Ericsson |
| R2-2409128 |
Work Plan for Rel-19 on NR MIMO Phase 5 |
CMCC, Samsung, MediaTek Inc. |
| 8.12.2 |
Initial analysis on RAN2 impact |
|
| R2-2408022 |
Discussion on the pathloss offset update via MAC CE and RRC |
Xiaomi |
| R2-2408092 |
RAN2 Impacts of Rel-19 NR MIMO |
CMCC |
| R2-2408125 |
Discussion on UE-initiated/event-driven beam management |
vivo |
| R2-2408181 |
Discussion on MAC CE impact for PL offset updates |
CATT |
| R2-2408196 |
Discussion on UE-initiated/event-driven beam management |
SHARP Corporation |
| R2-2408402 |
Initial Analysis on the RAN2 Impact for the R19 MIMO |
ZTE Corporation |
| R2-2408511 |
Initial analysis on RAN2 impact for Rel-19 NR MIMO Ph5 |
Huawei, HiSilicon |
| R2-2408649 |
RAN2 Aspects of the NR MIMO |
Nokia Corporation |
| R2-2408667 |
User plane and Control plane impacts from MIMO |
Ericsson |
| R2-2408723 |
Enhancement for Asymmetric DL sTRP/UL mTRP |
Sony |
| R2-2408795 |
Discussion on the design considerations for MIMO Phase 5 |
Qualcomm Incorporated |
| R2-2409023 |
Discussion on RAN2 impacts |
Samsung |
| R2-2409093 |
Consideration on RAN2 impact in MIMO phase 5 |
LG Electronics Inc. |
| R2-2409168 |
Triggering condition of PHR for UL-only TRP |
NTT DOCOMO INC. |
| R2-2409200 |
Initial analysis on RAN2 impact for Rel-19 NR MIMO Ph5 |
Huawei, HiSilicon |
| 8.14 |
Additional topological enhancements |
|
| R2-2407926 |
Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell (R3-244830; contact: Ericsson) |
RAN3 |
| 8.16 |
BDS B2b in A-GNSS |
|
| R2-2408036 |
Introduction of B2b signal in BDS system in A-GNSS |
CATT, CAICT, Ericsson |
| R2-2408221 |
Introduction of BDS B2b in A-GNSS positioning |
ZTE Corporation |
| R2-2408299 |
Introduction of BDS B2b signal in A-GNSS for BDS system |
CAICT,CATT |
| R2-2408660 |
Discussion on BDS B2b in A-GNSS |
NEC |
| R2-2408791 |
Discussion on support of BDS B2b in A-GNSS |
Huawei, HiSilicon |
| R2-2408792 |
Introduction of BDS B2b in A-GNSS for TS 38305 |
Huawei, HiSilicon |
| R2-2408793 |
Introduction of BDS B2b in A-GNSS for TS 36305 |
Huawei, HiSilicon |
| R2-2408933 |
Introduction of LCS User Plane |
Ericsson, Intel Corporation, Huawei, HiSilicon, ZTE Corporation, vivo, Qualcomm Incorporated |
| R2-2409199 |
LPP Impacts for B2b Signal addition |
Ericsson |
| R2-2409209 |
Discussion on introduction of BDS B2b signal in A-GNSS |
CAICT, CATT |
| R2-2409394 |
Introduction of LCS User Plane |
Ericsson, Intel Corporation, Huawei, HiSilicon, ZTE Corporation, vivo, Qualcomm Incorporated, Samsung |
| 9.1 |
Session on V2X/SL, R19 NES and MOB |
|
| R2-2409211 |
Report from session on V2X/SL, R19 NES and MOB |
Vice Chairman (Samsung) |
| 9.2 |
Session on R18 MIMOevo, R18 MUSIM, and R19 LP-WUS |
|
| R2-2409212 |
Rel-18 MIMO and MUSIM, Rel-19 MIMO, LPWUS, and SBFD |
Vice Chairman (CATT) |
| 9.3 |
Session on NR NTN and IoT NTN |
|
| R2-2409213 |
Report from session on NR NTN and IoT NTN |
Session chair (ZTE) |
| 9.4 |
Session on positioning and sidelink relay |
|
| R2-2409214 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 9.5 |
Session on R18 MBS, R18 QoE and R19 XR |
|
| R2-2409215 |
Report from session on R18 MBS, R18 QoE and R19 XR |
Session chair (Huawei) |
| 9.6 |
Session on maintenance and SON/MDT |
|
| R2-2409216 |
Report from session on maintenance and SON/MDT |
Session chair (Ericsson) |